Exemple
Exercise Django 6.1 requests and migrate signed cookies without reviving ambiguous name-and-salt collisions
sha256:b2ddcde01ebb61c661640e408c08c66d8bb5bac908bb123b63ee44f86559d282
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Cas
- Objectif
- Exercise Django 6.1 requests and migrate signed cookies without reviving ambiguous name-and-salt collisions HOW
- Paquets
- django 6.1
- Environnement
- python 3.12
- Créé
- 2026-08-17T02:14:30Z
Ce que l'on suppose souvent
A signed cookie remains valid when copied to any cookie name whose name-plus-salt text matches the original pair, and enabling legacy compatibility is a silent permanent fix.
L'auteur de l'échantillon a consigné ici ce qu'un développeur ou un modèle s'attendrait à voir. Le contrat ci-dessous est ce qui s'est réellement exécuté.
Contrat
- RequestFactory and Client execute without a server or database, keep POST form data separate from repeated query_params, let per-call query_params replace constructor defaults, and negotiate the Accept header.
- HttpResponse.set_signed_cookie and HttpRequest.get_signed_cookie round-trip a value only when the cookie name and caller salt match.
- Django 6.1 rejects a new signed cookie copied from the ('userid', 'v1') pair to the legacy-colliding ('user', 'idv1') pair.
- A cookie made with the old ambiguous 'useridv1' signer salt is rejected by Django 6.1's default settings.
- SIGNED_COOKIE_LEGACY_SALT_FALLBACK=True temporarily accepts the old cookie and emits RemovedInDjango70Warning.
Fichiers
- NOTES.md
- csx.json
- requirements.in
- requirements.lock
- requirements.txt
- test/contract.py
Télécharger l'artefact vérifié (tar.gz) — les octets exacts sur lesquels le contrat s'est exécuté
Seeder d'origine
Reçus de vérification
- python 3.12 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9