-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: HttpContent.SetHeader failing when secret header already exists #1479
Comments
@ajkauffmann has agreed to include this in a pull request he is working on anyway 🥳 |
I'm active now. 😊 |
And now I could assign you 🥳 |
@ajkauffmann thank you for picking this one. We tried to use it internally to promote open-source contribution within an organization but it was pushed down in priority. |
Is this issue fixed, because i have the same issue when i try to use a secretbody with Application/JSON as content-type. If requesting support, please provide the following details to help troubleshooting: Error message: Internal session ID: Application Insights session ID: Client activity id: Time stamp on error: User telemetry id: AL call stack: |
Yes, a PR will be created next week! |
Thank you for the Solution, this is just a major issue because i have a Customer who needs this solution ASAP and security is key. |
You can always use a workaround by creating a HttpContent object with the correct and use it with HttpContent.Create(HttpContent). Then you don't have to wait for the PR to be approved and backported to v25. |
Describe the issue
The "Http Content" codeunit throws an error message when content is defined from SecretText.
This happens because inside "Http Content Impl.".SetHeader procedure
Headers.Contains(Name)
condition will return false for a secret header, which will be automatically created when we set a content from the SecretText value.Expected behavior
Content will be defined with a new header without error.
Steps to reproduce
Additional context
No response
I will provide a fix for a bug
The text was updated successfully, but these errors were encountered: