Django 6.1 ドキュメント

Home | Table of contents | Index | Modules

« previous | up | next »

Results of 1 - 10 of about 24 for independent (0.001 sec.)

Django 1.3.4 リリースノート — Django 6.1 ドキュメント 11659: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.4 リリースノート ¶ October 17, 2012 This is the fourth release in the Django 1.3 series. Host header poisoning ¶ Some parts of Django -- ... rsing password parts URLs users HttpRequest host username validsite リリースノート October fourth release series poisoning independent user written applications make including domain attacks クイック検索 Last update: 2026年10月09日 « previous | up | next » ...; https://man.mtool.work/django/6.1/releases/1.3.4.html

Django 1.4.2 リリースノート — Django 6.1 ドキュメント 11159: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.2 リリースノート ¶ October 17, 2012 This is the second security release in the Django 1.4 series. Host header poisoning ¶ Some parts of D ... jango -- independent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host h ... n users HttpRequest host username validsite issue changes arguments リリースノート October second release series poisoning independent user クイック検索 Last update: 2026年10月09日 « previous | up | next » ...; https://man.mtool.work/django/6.1/releases/1.4.2.html

Django 1.3.5 リリースノート — Django 6.1 ドキュメント 10908: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl ... ngoing reports of problems, and in the other we've chosen to take further steps to tighten up Django's code in response to independent discovery of potential problems from multiple sources. Host header poisoning ¶ Several earlier Django security releases fo ... cations and many third-party applications, accepting a user-supplied redirect target is a common pattern). Since then, two independent audits of the code turned up further potential problems. So, similar to the Host-header issue, we are taking steps to prov ...; https://man.mtool.work/django/6.1/releases/1.3.5.html

Django 1.4.3 リリースノート — Django 6.1 ドキュメント 10908: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl ... ngoing reports of problems, and in the other we've chosen to take further steps to tighten up Django's code in response to independent discovery of potential problems from multiple sources. Host header poisoning ¶ Several earlier Django security releases fo ... cations and many third-party applications, accepting a user-supplied redirect target is a common pattern). Since then, two independent audits of the code turned up further potential problems. So, similar to the Host-header issue, we are taking steps to prov ...; https://man.mtool.work/django/6.1/releases/1.4.3.html

Django 1.3.5 リリースノート — Django 6.1 ドキュメント 10642: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl ... ngoing reports of problems, and in the other we've chosen to take further steps to tighten up Django's code in response to independent discovery of potential problems from multiple sources. Host header poisoning ¶ Several earlier Django security releases fo ... cations and many third-party applications, accepting a user-supplied redirect target is a common pattern). Since then, two independent audits of the code turned up further potential problems. So, similar to the Host-header issue, we are taking steps to prov ...; https://man.mtool.work/django/6.1/releases/1.3.5.html

Django 1.4.3 リリースノート — Django 6.1 ドキュメント 10642: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl ... ngoing reports of problems, and in the other we've chosen to take further steps to tighten up Django's code in response to independent discovery of potential problems from multiple sources. Host header poisoning ¶ Several earlier Django security releases fo ... cations and many third-party applications, accepting a user-supplied redirect target is a common pattern). Since then, two independent audits of the code turned up further potential problems. So, similar to the Host-header issue, we are taking steps to prov ...; https://man.mtool.work/django/6.1/releases/1.4.3.html

Django 1.3.4 リリースノート — Django 6.1 ドキュメント 8857: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.4 リリースノート ¶ October 17, 2012 This is the fourth release in the Django 1.3 series. Host header poisoning ¶ Some parts of Django -- ...; https://man.mtool.work/django/6.1/releases/1.3.4.html

Django 1.4.2 リリースノート — Django 6.1 ドキュメント 8607: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.2 リリースノート ¶ October 17, 2012 This is the second security release in the Django 1.4 series. Host header poisoning ¶ Some parts of D ... jango -- independent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host h ...; https://man.mtool.work/django/6.1/releases/1.4.2.html

Django 1.3.6 リリースノート — Django 6.1 ドキュメント 8356: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.6 リリースノート ¶ February 19, 2013 Django 1.3.6 fixes four security issues present in previous Django releases in the 1.3 series. This ... is the sixth bugfix/security release in the Django 1.3 series. Host header poisoning ¶ Some parts of Django -- independent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host h ...; https://man.mtool.work/django/6.1/releases/1.3.6.html

Django 1.3.6 リリースノート — Django 6.1 ドキュメント 8356: Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.6 リリースノート ¶ February 19, 2013 Django 1.3.6 fixes four security issues present in previous Django releases in the 1.3 series. This ... is the sixth bugfix/security release in the Django 1.3 series. Host header poisoning ¶ Some parts of Django -- independent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host h ...; https://man.mtool.work/django/6.1/releases/1.3.6.html

PREV 1 2 3 NEXT

« previous | up | next »