[3006.x] Fix content-type backwards compatability #66163
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
salt-project-bot-prod-environment
bot
changed the title
whytewolf
reviewed
Mar 1, 2024
dwoz
force-pushed
the
issue/3006.x/66127
branch
from
96bb87d to
d262e24
Compare
whytewolf
approved these changes
Mar 13, 2024
s0undt3ch
approved these changes
Mar 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Set content type on proxy requests that do not provide a content type header. This fixes backwards compatibility with old curl client.
What issues does this PR fix or reference?
Fixes: #66127
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.