feedback
feedback copied to clipboard
Install Site Extension returns 400 Bad Request
Describe the bug
The Try It feature of the installsiteextension
endpoint returns a cryptic HTTP 400 status.
The Try It feature works for both start
and stop
for the same site.
To Reproduce Steps to reproduce the behavior:
- Go to https://docs.microsoft.com/en-us/rest/api/appservice/webapps/installsiteextension
- Click on Try It
- Enter valid Azure App Service name
- Enter valid Azure App Service resource group name
- Enter valid Azure App Service Site Extension Id
- See error
Expected behavior The site extension should attempt install or return some actionable error.
Screenshots
Attempt to install the site extension
400 Response
Desktop (please complete the following information):
- OS: Windows Pro
- Browser: Chrome
- Version 10.0.19041
Thank you for creating the issue! One of our team members will get back to you shortly with additional information. If this is a product issue, please close this and contact the particular product's support instead (see https://support.microsoft.com/allproducts for the list of support websites).
Hello, any updates on this issue?
Hi, checking in again for any updates on this issue.
Hi, any updates on this issue?
Hi I'm running into the same issue and repeated the steps above, and I'm getting the same issue. Anyone out there that can look into this, please?
Hi, I'm running in exactly the same issue, any update??
I'm running into this problem also. I can install the app service site extension using the azure cli ("az resource create ... ") but when i try the same using the "Try It" function in https://docs.microsoft.com/en-us/rest/api/appservice/webapps/installsiteextension , it gives me a Response Code of 400 with no information as to why. Could someone look into this please?
Same issue here...
I will also add that the API itself is broken when trying it from azure cli.
So the docs website is definitely broken but if you use something like Postman and submit the request with {}
as the request's body, it'll work. Looks like the server requires a JSON body even if it's unused.