microsoft / microsoft/PowerPlatformConnectors
setheader not allowed for 'content-length' header parameter.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
When calling the Azure File Share REST API using a custom connector in Power Automate to create a blank file with the PUT method, the request must include the header Content-Length: 0. However, Power Automate automatically assumes an empty body ({}) and sets Content-Length: 2. This causes the API to reject the request with a 400 Bad Request error. How to overcome this issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Azure File Share REST API PUT request through a Power Automate custom connector, comparing the required Content-Length: 0 with the generated Content-Length: 2. Done means the blank-file request can send the required zero-length header and no longer receives a 400 Bad Request response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100