Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

301&302 vs 307&308 #32

Open
andreineculau opened this issue Sep 27, 2013 · 2 comments
Open

301&302 vs 307&308 #32

andreineculau opened this issue Sep 27, 2013 · 2 comments
Labels
question
Milestone
v5

Comments

@andreineculau
Copy link
Member

given 307 & 308, is there a good reason beyond “legacy” compatibility to support 301 & 302?

the diagram went KISS and chose 307 & 308 in 49cc4b7
@andreineculau
Copy link
Member Author

relevant:

http://trac.tools.ietf.org/wg/httpbis/trac/ticket/160
http://stackoverflow.com/questions/8138137/http-post-request-receives-a-302-should-the-redirect-request-be-a-get
http://www.mnot.net/javascript/xmlhttprequest/

@andreineculau
Copy link
Member Author

From https://twitter.com/dret/status/384688006788952064
@andreineculau if the behavior of the moved resource changed (new URI template, for example), maybe it makes sense to GET it first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
v5
Development

No branches or pull requests
1 participant
@andreineculau