The "302 Found" redirect is used by default in ​django.http.response HttpResponseRedirect.
Could we discuss changing this to use "303 See Other" redirects? 303 redirects are more in-line with the intent of the redirect after a change, and also 303 redirects disallow browser caching. If a browser serves a cached response without revalidation, then the server would not receive the request. 303 redirects are not supported by HTTP/1.0, but all modern browsers now support HTTP/1.1 or higher. What does everyone think about changing 302 redirects to 303? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/829cedfb-855b-496a-9bf9-f60c6772f212%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
