Azure / Azure/azure-rest-api-specs
Web Site Extension installation returns Bad Request when called without content
Open
Service Attention
Web Apps
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 3d 37m
- Merged PRs (30d)
- 446
Description
As suggested by @hovsepm [here](https://github.com/Azure/azure-libraries-for-net/issues/241#issuecomment-378684495), Azure SDK calls fail to create site extensions when they attempt to PUT a request with null content. Setting request body to an empty JSON object (`{}`) fixes the problem.
Contributor guide
Research direction
No file or test is named. Locate the Web Site Extension installation PUT operation in the Azure REST API specifications, inspect how its null request body is defined, and verify that the specification requires an empty JSON object so the request no longer returns Bad Request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100