Ejemplo
Exercise Django 6.1 requests and migrate signed cookies without reviving ambiguous name-and-salt collisions
sha256:b2ddcde01ebb61c661640e408c08c66d8bb5bac908bb123b63ee44f86559d282
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Exercise Django 6.1 requests and migrate signed cookies without reviving ambiguous name-and-salt collisions HOW
- Paquetes
- django 6.1
- Entorno
- python 3.12
- Creado
- 2026-08-17T02:14:30Z
Lo que suele suponerse
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.
El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.
Contrato
- 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.
Archivos
- NOTES.md
- csx.json
- requirements.in
- requirements.lock
- requirements.txt
- test/contract.py
Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato
Seeder de origen
Recibos de verificación
- python 3.12 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9