[Bug]: HttpContent.SetHeader failing when secret header already exists #1479
Labels
Approved
The issue is approved
Bug
Something isn't working
Integration
GitHub request for Integration area
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: