per page, with , order by , clip by
Results of 1 - 10 of about 34 for signed (0.005 sec.)
Django 5.2.15 release notes — Django 6.1 ドキュメント 11663
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.15 release notes ¶ June 3, 2026 Django 5.2.15 fixes five security issues with severity "low" in 5.2.14. CVE-2026-6873: Signed cookie salt ... namespace collision ¶ get_signed_cookie() derived the signing salt by concatenating the cookie name ( key ) and salt arguments. When distinct name and salt ... pairs produced the same concatenation, cookies could be accepted in a context different from the one where they were signed. Cookies are now signed with an unambiguous salt derivation. For backwards compatibility, cookies signed by older Django v ... ersions are accepted until Django 2028. Projects affected by the above ambiguity should set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject older cookies immediately. This issue has severity "low" according to the D ...
https://man.mtool.work/django/6.1/releases/5.2.15.html
Django 5.2.15 release notes — Django 6.1 ドキュメント 11519
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.15 release notes ¶ June 3, 2026 Django 5.2.15 fixes five security issues with severity "low" in 5.2.14. CVE-2026-6873: Signed cookie salt ... namespace collision ¶ get_signed_cookie() derived the signing salt by concatenating the cookie name ( key ) and salt arguments. When distinct name and salt ... pairs produced the same concatenation, cookies could be accepted in a context different from the one where they were signed. Cookies are now signed with an unambiguous salt derivation. For backwards compatibility, cookies signed by older Django v ... ersions are accepted until Django 2028. Projects affected by the above ambiguity should set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject older cookies immediately. This issue has severity "low" according to the D ...
https://man.mtool.work/django/6.1/releases/5.2.15.html
Django 6.0.6 release notes — Django 6.1 ドキュメント 11519
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.0.6 release notes ¶ June 3, 2026 Django 6.0.6 fixes five security issues with severity "low" and one bug in 6.0.5. Also, the latest string ... translations from Transifex are incorporated. CVE-2026-6873: Signed cookie salt namespace collision ¶ get_signed_cookie() derived the signing salt by concatenating the cookie name ( key ) an ... salt pairs produced the same concatenation, cookies could be accepted in a context different from the one where they were signed. Cookies are now signed with an unambiguous salt derivation. For backwards compatibility, cookies signed by older Django v ... ersions are accepted until Django 2028. Projects affected by the above ambiguity should set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject older cookies immediately. This issue has severity "low" according to the D ...
https://man.mtool.work/django/6.1/releases/6.0.6.html
Django 6.0.6 release notes — Django 6.1 ドキュメント 11375
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.0.6 release notes ¶ June 3, 2026 Django 6.0.6 fixes five security issues with severity "low" and one bug in 6.0.5. Also, the latest string ... translations from Transifex are incorporated. CVE-2026-6873: Signed cookie salt namespace collision ¶ get_signed_cookie() derived the signing salt by concatenating the cookie name ( key ) an ... salt pairs produced the same concatenation, cookies could be accepted in a context different from the one where they were signed. Cookies are now signed with an unambiguous salt derivation. For backwards compatibility, cookies signed by older Django v ... ersions are accepted until Django 2028. Projects affected by the above ambiguity should set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject older cookies immediately. This issue has severity "low" according to the D ...
https://man.mtool.work/django/6.1/releases/6.0.6.html
暗号署名 — Django 6.1 ドキュメント 10720
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 暗号署名 ¶ ウェブアプリケーションのセキュリティの黄金律は、信頼できない情報源からのデータを決して信頼しないことです。時には、信頼されていない媒体を通 ... に文字列でない値を渡すと、その値は署名される前に強制的に文字列に変換され、 unsign の結果にはその文字列の値が返されます。 >>> signed = signer . sign ( 2.5 ) >>> original = signer . unsign ( signed ) >>> original '2.5' リスト、タプル、辞書を保護したい場合は ... 、 sign_object() と unsign_object() メソッドを使います。 >>> signed_obj = signer . sign_object ({ "message" : "Hello!" }) >>> signed_obj 'eyJtZXNzYWdlIjoiSGVsbG8hIn0:bzb48DBkB-bwLaCnUVB75r5V ... APUEpzWJPrTb80JMIXM' >>> obj = signer . unsign_object ( signed_obj ) >>> obj {'message': 'Hello!'} 詳細は 複雑なデータ構造の保護 を参照してください。 何らかの理由により署名の値が書き換わ ...
https://man.mtool.work/django/6.1/topics/signing.html
暗号署名 — Django 6.1 ドキュメント 10720
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 暗号署名 ¶ ウェブアプリケーションのセキュリティの黄金律は、信頼できない情報源からのデータを決して信頼しないことです。時には、信頼されていない媒体を通 ... に文字列でない値を渡すと、その値は署名される前に強制的に文字列に変換され、 unsign の結果にはその文字列の値が返されます。 >>> signed = signer . sign ( 2.5 ) >>> original = signer . unsign ( signed ) >>> original '2.5' リスト、タプル、辞書を保護したい場合は ... 、 sign_object() と unsign_object() メソッドを使います。 >>> signed_obj = signer . sign_object ({ "message" : "Hello!" }) >>> signed_obj 'eyJtZXNzYWdlIjoiSGVsbG8hIn0:bzb48DBkB-bwLaCnUVB75r5V ... APUEpzWJPrTb80JMIXM' >>> obj = signer . unsign_object ( signed_obj ) >>> obj {'message': 'Hello!'} 詳細は 複雑なデータ構造の保護 を参照してください。 何らかの理由により署名の値が書き換わ ...
https://man.mtool.work/django/6.1/topics/signing.html
リクエストとレスポンスのオブジェクト — Django 6.1 ドキュメント 8707
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » リクエストとレスポンスのオブジェクト ¶ 簡単な概要 ¶ Django は、システムを通じてステータスを渡すために、リクエストとレスポンスのオブジェクトを使います ... you need to redirect users to HTTPS, it's best to let your web server redirect all HTTP traffic to HTTPS. HttpRequest. get_signed_cookie ( key , default = RAISE_ERROR , salt = '' , max_age = None ) [ソース] ¶ 署名付きクッキーの値を返します。署名が無効で ... used to put the cookie into a separate signature namespace. If supplied, the max_age argument will be checked against the signed timestamp attached to the cookie value to ensure the cookie is not older than max_age seconds. Cookies signed by older Dja ... ngo versions are accepted by default for backwards compatibility. Set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject them. 例: >>> request . get_signed_cookie ( "name" ) 'Tony' >>> request . g ...
https://man.mtool.work/django/6.1/ref/request-response.html
リクエストとレスポンスのオブジェクト — Django 6.1 ドキュメント 8707
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » リクエストとレスポンスのオブジェクト ¶ 簡単な概要 ¶ Django は、システムを通じてステータスを渡すために、リクエストとレスポンスのオブジェクトを使います ... you need to redirect users to HTTPS, it's best to let your web server redirect all HTTP traffic to HTTPS. HttpRequest. get_signed_cookie ( key , default = RAISE_ERROR , salt = '' , max_age = None ) [ソース] ¶ 署名付きクッキーの値を返します。署名が無効で ... used to put the cookie into a separate signature namespace. If supplied, the max_age argument will be checked against the signed timestamp attached to the cookie value to ensure the cookie is not older than max_age seconds. Cookies signed by older Dja ... ngo versions are accepted by default for backwards compatibility. Set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject them. 例: >>> request . get_signed_cookie ( "name" ) 'Tony' >>> request . g ...
https://man.mtool.work/django/6.1/ref/request-response.html
Django 6.1 release notes — Django 6.1 ドキュメント 7924
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.1 release notes ¶ August 5, 2026 Welcome to Django 6.1! These release notes cover the new features , as well as some backwards incompatible ... he redirect() shortcut, now accept a max_length parameter to override the default maximum URL length limit. セキュリティ ¶ Signed cookies now use an unambiguous salt derivation by default. Set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to True to continue acce ... pting legacy signed cookies. シリアライズ (シリアル化) ¶ Subclasses of models defining the natural_key() method can now opt out of natural key ... The minimum supported version of SQLite is increased from 3.31.0 to 3.37.0. The default value of the transitional setting SIGNED_COOKIE_LEGACY_SALT_FALLBACK is now False . In cases where cached pages or template fragments varied on arguments, e.g. var ...
https://man.mtool.work/django/6.1/releases/6.1.html
Django 6.1 release notes — Django 6.1 ドキュメント 7924
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.1 release notes ¶ August 5, 2026 Welcome to Django 6.1! These release notes cover the new features , as well as some backwards incompatible ... he redirect() shortcut, now accept a max_length parameter to override the default maximum URL length limit. セキュリティ ¶ Signed cookies now use an unambiguous salt derivation by default. Set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to True to continue acce ... pting legacy signed cookies. シリアライズ (シリアル化) ¶ Subclasses of models defining the natural_key() method can now opt out of natural key ... The minimum supported version of SQLite is increased from 3.31.0 to 3.37.0. The default value of the transitional setting SIGNED_COOKIE_LEGACY_SALT_FALLBACK is now False . In cases where cached pages or template fragments varied on arguments, e.g. var ...
https://man.mtool.work/django/6.1/releases/6.1.html
PREV 1 2 3 4 NEXT