Force setting of content-type: application/json for SAM to avoid http 415 error #22
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
aherbst-broad
requested review from
a team,
raaidbroad,
eparkmonster and
quazi-h
and removed request for
a team
raaidbroad
approved these changes
Jun 17, 2021
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.
Why
Relevant ticket
We are getting an HTTP 415 error code when setting snapshots public. I have determined this is due to us not sending an
Content-type: application/jsonheader in our request.This PR
requestswill generally do the right thing if you send ajson={...}payload, but we're sending a rawdata=truevalue which short-circuits the automatic setting of the header)