#33562: set_cookie and set_signed_cookie should accept timedelta object for
max_age
argument
-------------------------------------+-------------------------------------
Reporter: Luke Plant | Owner: Luke
| Plant
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"f3bf6c4218404479f7841e0af213d5db65913278" f3bf6c42]:
{{{
#!CommitTicketReference repository=""
revision="f3bf6c4218404479f7841e0af213d5db65913278"
Refs #33562 -- Made HttpResponse.set_cookie() raise ValueError when both
"expires" and "max_age" are passed.
This fixes the case where you might pass set_cookie(expires=val,
max_age=val)
and max_age is silently ignored.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33562#comment:6>
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/0107017f63a6571b-28e9bade-3ff9-45a4-bed5-7ec9df53da37-000000%40eu-central-1.amazonses.com.
