id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 6227,Make HttpResponseRedirect RFC compilant.,Piotr Lewandowski ,nobody,"The [http://rfc.net/rfc2616.html#s10.3.4 RFC2616] states in 10.3.4 that: {{{ The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. }}} [http://www.djangoproject.com/documentation/request_response/#httpresponse-subclasses HttpResponseRedirect] is often used as a redirection after POST request (such case is present in [http://www.djangoproject.com/documentation/tutorial04/#write-a-simple-form tutorial]). Current code: {{{ #!python class HttpResponseRedirect(HttpResponse): status_code = 302 }}} Should be: {{{ #!python class HttpResponseRedirect(HttpResponse): status_code = 303 }}} Unfortunately this change is backwards-incompatible.",,closed,HTTP handling,dev,,invalid,rfc2616 http redirect post,,Design decision needed,1,0,0,0,0,0