#31260: Enable cookie security if HTTPS is explicity indicated in settings.
-------------------------------------+-------------------------------------
Reporter: Adam Yala | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: 3.0
Severity: Normal | Resolution: wontfix
Keywords: ssl https cookie | Triage Stage:
settings | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Adam (Chainz) Johnson):
* cc: Adam (Chainz) Johnson (added)
Comment:
A cleaner alternative I thought of would be to introduce the new value
`None` as the defaults for these settings, which could mean the secure
flag is set on the cookies if `request.is_secure()`. The only potential
breakage is for sites that are served on HTTP and HTTPS, which is
something of a misconfiguration these days.
--
Ticket URL: <https://code.djangoproject.com/ticket/31260#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.7f13fb95dd6d0c266bfd1035434fc0ce%40djangoproject.com.
