サンプル
Exercise Django 6.1 requests and migrate signed cookies without reviving ambiguous name-and-salt collisions
sha256:b2ddcde01ebb61c661640e408c08c66d8bb5bac908bb123b63ee44f86559d282
PUBLISHED
L3_CONTRACT_PASS
MIT-0
ケース
- ゴール
- Exercise Django 6.1 requests and migrate signed cookies without reviving ambiguous name-and-salt collisions HOW
- パッケージ
- django 6.1
- 環境
- python 3.12
- 作成日
- 2026-08-17T02:14:30Z
よくある思い込み
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.
このサンプルの作者が、ここで開発者やモデルが期待するであろうこととして記録したもの。下の契約が実際に実行されたものだ。
コントラクト
- 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.
ファイル
- NOTES.md
- csx.json
- requirements.in
- requirements.lock
- requirements.txt
- test/contract.py
検証済みアーティファクトをダウンロード (tar.gz) — 契約が実行された正確なバイト列
オリジンシーダー
検証レシート
- python 3.12 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9