search

for-GET / http-decision-diagram

An activity diagram to describe the resolution of HTTP response status codes, given various headers.
https://github.com/for-GET/http-decision-diagram/blob/master/doc/2013-06-10-http-hell-no.md
Apache License 2.0
3.63k stars 196 forks source link

301&302 vs 307&308 #32

Open andreineculau opened 11 years ago

andreineculau commented 11 years ago

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

the diagram went KISS and chose 307 & 308 in https://github.com/for-GET/http-decision-diagram/commit/49cc4b703c7c67239bea9904b2ac1a162a475196

andreineculau commented 11 years ago

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 commented 11 years ago

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.