#21587: Make generic RedirectView default to permanent=False
--------------------------------------+------------------------------------
Reporter: wraus@… | Owner: Melevir
Type: Cleanup/optimization | Status: assigned
Component: Generic views | Version: 1.6
Severity: Normal | Resolution:
Keywords: redirect, view | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timo):
* cc: timo (added)
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
Russ and I discussed this on IRC.
From him: "Given the way that browsers hard cache permanent redirects, I
think there's potential for a footgun in having permanent the default. So
yes, I think [making this change is] worth it. As for migration strategy -
Our process would dictate a full 2 release deprecation seems excessive for
this. We've made exceptions for some small things in the past (e.g.,
changes to the profane words list) and given that we have the checks
command as well, a 1 release warning cycle seems appropriate to me. The
full "from future" approach seems excessive.
me: so if a subclass doesn't specify the permanent flag, we'd warn now,
then change the default in 1.8.
--
Ticket URL: <https://code.djangoproject.com/ticket/21587#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/084.caf871ea3590311bc51e374a3358472a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
