Fixed redirect handling for HTTP status code 303 #109
Merged
Conversation
This file contains hidden or 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
added 4 commits
January 16, 2013 14:20
- HTTP status code 303: redirect SHOULD be done with GET method
- default data value = {} to avoid wrong content-length headers
danwrong
added a commit
that referenced
this pull request
Feb 20, 2013
Fixed redirect handling for HTTP status code 303
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixed the redirect handling for HTTP status coded 303.
The client has to follow the header location redirect with the GET method.
For example when we trigger a call to POST example.com/resource we have to follow the header location /resource/1 with GET instead of POST.