per page, with , order by , clip by
Results of 1 - 10 of about 44 for parts (0.003 sec.)
Django 1.3.4 リリースノート — Django 6.1 ドキュメント 12678
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 -- ... cepted by Django when running on validsite.com : Host: validsite.com:random@evilsite.com Using this, an attacker can cause parts of Django -- particularly the password-reset mechanism -- to generate and display arbitrary URLs to users. To remedy this, ... ピックへ Django 1.3.5 リリースノート 次のトピックへ Django 1.3.3 リリースノート 関連キーワード Host header parsing password parts URLs users HttpRequest host username validsite リリースノート October fourth release series poisoning independent user wri ...
https://man.mtool.work/django/6.1/releases/1.3.4.html
Django 1.3.4 リリースノート — Django 6.1 ドキュメント 12264
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 -- ... cepted by Django when running on validsite.com : Host: validsite.com:random@evilsite.com Using this, an attacker can cause parts of Django -- particularly the password-reset mechanism -- to generate and display arbitrary URLs to users. To remedy this, ... Django 1.3.5 リリースノート 次のトピックへ Django 1.3.3 リリースノート 関連キーワード Django Host header parsing password parts URLs users django HttpRequest get host username validsite リリースノート October fourth release series poisoning 関連するペ ...
https://man.mtool.work/django/6.1/releases/1.3.4.html
Django 1.4.2 リリースノート — Django 6.1 ドキュメント 11849
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 ... cepted by Django when running on validsite.com : Host: validsite.com:random@evilsite.com Using this, an attacker can cause parts of Django -- particularly the password-reset mechanism -- to generate and display arbitrary URLs to users. To remedy this, ... 1.4.3 リリースノート 次のトピックへ Django 1.4.1 リリースノート 関連キーワード Host header Fixed parsing password security parts URLs documentation users HttpRequest host username validsite issue changes arguments リリースノート October second release ...
https://man.mtool.work/django/6.1/releases/1.4.2.html
Django 1.4.2 リリースノート — Django 6.1 ドキュメント 11649
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 ... cepted by Django when running on validsite.com : Host: validsite.com:random@evilsite.com Using this, an attacker can cause parts of Django -- particularly the password-reset mechanism -- to generate and display arbitrary URLs to users. To remedy this, ... ースノート 次のトピックへ Django 1.4.1 リリースノート 関連キーワード Django Host header Fixed name parsing password security parts URLs documentation users django HttpRequest get host username validsite now issue 関連するページ Django 1.3.4 リリースノー ...
https://man.mtool.work/django/6.1/releases/1.4.2.html
非同期サポート — Django 6.1 ドキュメント 9390
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 非同期サポート ¶ Django has support for writing asynchronous ("async") views, along with an entirely async-enabled request stack if you are running ... l per-request adaptation cost (see パフォーマンス ), and without the ability to have efficient long-running requests. Many parts of Django provide asynchronous APIs, including the ORM , the cache framework, authentication, sessions, and signals. For o ... ングレスポンスでクライアントの切断をハンドリングする こともできます。 非同期安全性 ¶ DJANGO_ALLOW_ASYNC_UNSAFE ¶ Certain key parts of Django are not able to operate safely in an async environment, as they have global state that is not coroutine-aware. T ... hese parts of Django are classified as "async-unsafe", and are protected from execution in an async environment. The synchronous API ...
https://man.mtool.work/django/6.1/topics/async.html
非同期サポート — Django 6.1 ドキュメント 8775
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 非同期サポート ¶ Django has support for writing asynchronous ("async") views, along with an entirely async-enabled request stack if you are running ... l per-request adaptation cost (see パフォーマンス ), and without the ability to have efficient long-running requests. Many parts of Django provide asynchronous APIs, including the ORM , the cache framework, authentication, sessions, and signals. For o ... ングレスポンスでクライアントの切断をハンドリングする こともできます。 非同期安全性 ¶ DJANGO_ALLOW_ASYNC_UNSAFE ¶ Certain key parts of Django are not able to operate safely in an async environment, as they have global state that is not coroutine-aware. T ... hese parts of Django are classified as "async-unsafe", and are protected from execution in an async environment. The synchronous API ...
https://man.mtool.work/django/6.1/topics/async.html
Django 1.3 リリースノート — Django 6.1 ドキュメント 7960
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3 リリースノート ¶ March 23, 2011 Django 1.3 へようこそ! Nearly a year in the making, Django 1.3 includes quite a few new features and plen ... distinction between not being passed data and being passed empty dictionary. This was inconsistent with behavior in other parts of the framework. Starting with 1.3 if you pass in empty dictionary the FormSet will raise a ValidationError . 以下は Form ... included with applications listed in the INSTALLED_APPS setting were changed. To provide a behavior consistent with other parts of Django that also use such setting (templates, etc.) now, when building the translation that will be made available, the ... r locating project-level translations is the directory containing the settings module) and there has been a shift in other parts of the framework to stop using it as a reference for location of assets at runtime. Detection of the locale subdirectory t ...
https://man.mtool.work/django/6.1/releases/1.3.html
Django 1.3.5 リリースノート — Django 6.1 ドキュメント 7960
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 ... d problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function, django.utils.http.is_safe_url , is added; this function takes a URL and a hostname, and checks ...
https://man.mtool.work/django/6.1/releases/1.3.5.html
Django 1.3 リリースノート — Django 6.1 ドキュメント 7960
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3 リリースノート ¶ March 23, 2011 Django 1.3 へようこそ! Nearly a year in the making, Django 1.3 includes quite a few new features and plen ... distinction between not being passed data and being passed empty dictionary. This was inconsistent with behavior in other parts of the framework. Starting with 1.3 if you pass in empty dictionary the FormSet will raise a ValidationError . 以下は Form ... included with applications listed in the INSTALLED_APPS setting were changed. To provide a behavior consistent with other parts of Django that also use such setting (templates, etc.) now, when building the translation that will be made available, the ... r locating project-level translations is the directory containing the settings module) and there has been a shift in other parts of the framework to stop using it as a reference for location of assets at runtime. Detection of the locale subdirectory t ...
https://man.mtool.work/django/6.1/releases/1.3.html
Django 1.4.3 リリースノート — Django 6.1 ドキュメント 7960
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 ... d problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function, django.utils.http.is_safe_url , is added; this function takes a URL and a hostname, and checks ...
https://man.mtool.work/django/6.1/releases/1.4.3.html
PREV 1 2 3 4 5 NEXT