Fix: Ensure Content-Type is set based on header value if not explicitly set #1704
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1697
This PR ensures that the
Content-Type
is set based on the header value if it is not explicitly set by the user.prepareRequestSpecs
method to check ifcontentType
is stillContentType.ANY
.ContentType
is not explicitly set by the user, it now retrieves theContent-Type
fromsessionHeaders
and applies it directly to theRequestSpecBuilder
.Content-Type
provided in the headers, preventing encoding and serialization issues.