| CARVIEW |
Select Language
HTTP/2 200
server: nginx
content-type: text/html;charset=utf-8
cache-control: must-revalidate
expires: Fri, 01 Jan 1999 00:00:00 GMT
set-cookie: trac_form_token=2d221596e64c14810f669a8c; HttpOnly; Path=/; Secure
set-cookie: trac_session=7114ba4494c77e01eaf7936b; expires=Tue, 21 Oct 2025 17:58:23 GMT; HttpOnly; Path=/; Secure
strict-transport-security: max-age=31536000; includeSubDomains; preload
permissions-policy: interest-cohort=()
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
accept-ranges: bytes
via: 1.1 varnish, 1.1 varnish
date: Wed, 23 Jul 2025 17:58:24 GMT
x-served-by: cache-fra-etou8220034-FRA, cache-bom-vanm7210089-BOM
x-cache: MISS, MISS
x-cache-hits: 0, 0
x-timer: S1753293504.698047,VS0,VE344
vary: Accept-Encoding
DjangoNonrelChanges – Django
Back to Top
Django
The web framework for perfectionists with deadlines.
Issues
Auth password reset URLs
- Problem
django.contrib.auth's password reset URLs contain a base36-encoded user ID (/reset/<user-id>/<token>/). The password reset feature breaks if the user ID is not an integer (because base36 can only express integers).- Solution
- Encode the user ID in a URL-safe variant of base64. This is a backwards-incompatible change that breaks "old-style" password reset URLs, but backwards compatibility should be very easy to implement if required.
- Alternative proposals
- None
Last modified
14 years ago
Last modified on Apr 28, 2011, 6:27:28 PM
Note:
See TracWiki
for help on using the wiki.
Download in other formats:
Django Links
Learn More
Get Involved
Follow Us
- Hosting by In-kind donors
- Design by Threespot &
© 2005-2025 Django SoftwareFoundation unless otherwise noted. Django is a registered trademark of the Django Software Foundation.