#19992: Put protection against unsafe redirects into `HttpResponseRedirectBase`
-------------------------------+------------------------------------
Reporter: coolRR | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: security | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by jacob):
* keywords: => security
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
I think this is a good idea.
However, we do need to think a bit about whether it should be enabled by
default. If we do, it'll break existing code, but if we don't then we're
violating "safe by default." My preference would be something like
`redirect(..., safe=False)` with `safe` defaulting to True, but that may
be too backwards-incompatible.
--
Ticket URL: <https://code.djangoproject.com/ticket/19992#comment:1>
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].
For more options, visit https://groups.google.com/groups/opt_out.
