#24145: Extend POST redirect error to be raised on PUT and PATCH
------------------------------+------------------------------------
Reporter: samuelcolvin | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
------------------------------+------------------------------------
Comment (by tomchristie):
I'm going to second this one. Our options are:
* Extend the check to also include `PUT` and `PATCH` and continue issuing
the 500 response.
* Extend the check to also include `PUT` and `PATCH`, but use an 307 (or
308) redirect, which is spec'ed as not allowing a rewrite-to-GET request.
See: http://trac.tools.ietf.org/html/draft-ietf-
httpbis-p2-semantics-21#section-7.4.7
Of these, the first is the lesser change. It's unclear to me how widely
supported 307/308 responses are supported by browsers and other clients.
--
Ticket URL: <https://code.djangoproject.com/ticket/24145#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.e053756b8de5bb071036a588c89a89b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
