per page, with , order by , clip by
Results of 1 - 10 of about 178 for server (0.004 sec.)
メールを送信する — Django 6.1 ドキュメント 11363
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » メールを送信する ¶ Django provides wrappers for Python's email and smtplib modules to simplify composing and sending email. Django's email framework ... ts swapping in different delivery mechanisms: you can direct email to the console or a file during development and an SMTP server or email service provider in production. コードは django.core.mail モジュールにあります。 簡単な例 ¶ 簡単なメール送信には ... ERS setting isn't defined). Use the MAILERS setting to tell Django how to send email. For example, to send through an SMTP server running on the local machine: MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIO ... , which sends using the standard SMTP protocol. This backend is useful for many production configurations, including SMTP servers in your own infrastructure and most commercial email service providers (ESPs). There are also third-party email backends ...
https://man.mtool.work/django/6.1/topics/email.html
メールを送信する — Django 6.1 ドキュメント 11029
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » メールを送信する ¶ Django provides wrappers for Python's email and smtplib modules to simplify composing and sending email. Django's email framework ... ts swapping in different delivery mechanisms: you can direct email to the console or a file during development and an SMTP server or email service provider in production. コードは django.core.mail モジュールにあります。 簡単な例 ¶ 簡単なメール送信には ... ERS setting isn't defined). Use the MAILERS setting to tell Django how to send email. For example, to send through an SMTP server running on the local machine: MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIO ... , which sends using the standard SMTP protocol. This backend is useful for many production configurations, including SMTP servers in your own infrastructure and most commercial email service providers (ESPs). There are also third-party email backends ...
https://man.mtool.work/django/6.1/topics/email.html
ロギング — Django 6.1 ドキュメント 9604
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » ロギング ¶ 参考 ロギングの設定と利用 Django のロギングの概要 Django の logging モジュールは Python の 組み込み logging モジュールを継承しています。 ... デフォルトのログ記録条件の完全なセットは以下の通りです: DEBUG が True のとき: django ロガーは、 django ヒエラルキー ( django.server を除く) において、 INFO レベル以上のメッセージをコンソールに送信します。 DEBUG が False のとき: django ロガーは、 django ヒ ... エラルキー ( django.server を除く) において、 ERROR ないし CRITICAL レベルを AdminEmailHandler に送信します。 DEBUG の値にかかわらず: django.server ロ ... ガーは INFO レベル以上のメッセージをコンソールに送信します。 django.server を除く全てのロガーは、ルートの django ロガーまで、親に対してログを伝播させます。 console と mail_admins ハンドラは、上述の ...
https://man.mtool.work/django/6.1/ref/logging.html
ロギング — Django 6.1 ドキュメント 9604
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » ロギング ¶ 参考 ロギングの設定と利用 Django のロギングの概要 Django の logging モジュールは Python の 組み込み logging モジュールを継承しています。 ... デフォルトのログ記録条件の完全なセットは以下の通りです: DEBUG が True のとき: django ロガーは、 django ヒエラルキー ( django.server を除く) において、 INFO レベル以上のメッセージをコンソールに送信します。 DEBUG が False のとき: django ロガーは、 django ヒ ... エラルキー ( django.server を除く) において、 ERROR ないし CRITICAL レベルを AdminEmailHandler に送信します。 DEBUG の値にかかわらず: django.server ロ ... ガーは INFO レベル以上のメッセージをコンソールに送信します。 django.server を除く全てのロガーは、ルートの django ロガーまで、親に対してログを伝播させます。 console と mail_admins ハンドラは、上述の ...
https://man.mtool.work/django/6.1/ref/logging.html
Django 1.11.1 リリースノート — Django 6.1 ドキュメント 8614
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.11.1 リリースノート ¶ May 6, 2017 Django 1.11.1 adds a minor feature and fixes several bugs in 1.11. Allowed disabling server-side cursors ... on PostgreSQL ¶ The change in Django 1.11 to make QuerySet.iterator() use server-side cursors on PostgreSQL prevents running Django with PgBouncer in transaction pooling mode. To reallow that, use the DI ... SABLE_SERVER_SIDE_CURSORS setting in DATABASES . See トランザクションプールとサーバーサイドカーソル for more discussion. バグ修正 ¶ Mad ... n using the foreign key's parent model as the lookup value ( #28175 ). 目次 Django 1.11.1 リリースノート Allowed disabling server-side cursors on PostgreSQL バグ修正 前のトピックへ Django 1.11.2 リリースノート 次のトピックへ Django 1.11 リリースノート ...
https://man.mtool.work/django/6.1/releases/1.11.1.html
Django 1.11.1 リリースノート — Django 6.1 ドキュメント 8514
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.11.1 リリースノート ¶ May 6, 2017 Django 1.11.1 adds a minor feature and fixes several bugs in 1.11. Allowed disabling server-side cursors ... on PostgreSQL ¶ The change in Django 1.11 to make QuerySet.iterator() use server-side cursors on PostgreSQL prevents running Django with PgBouncer in transaction pooling mode. To reallow that, use the DI ... SABLE_SERVER_SIDE_CURSORS setting in DATABASES . See トランザクションプールとサーバーサイドカーソル for more discussion. バグ修正 ¶ Mad ... n using the foreign key's parent model as the lookup value ( #28175 ). 目次 Django 1.11.1 リリースノート Allowed disabling server-side cursors on PostgreSQL バグ修正 前のトピックへ Django 1.11.2 リリースノート 次のトピックへ Django 1.11 リリースノート ...
https://man.mtool.work/django/6.1/releases/1.11.1.html
REMOTE_USER で認証する — Django 6.1 ドキュメント 8291
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » REMOTE_USER で認証する ¶ This document describes how to make use of external authentication sources in your Django applications. This type of authen ... IS and Integrated Windows Authentication or Apache and mod_authnz_ldap , CAS , WebAuth , mod_auth_sspi , etc. When the web server takes care of authentication it typically provides the authenticated user as REMOTE_USER . In Django, this value is made a ... UserMiddleware must not be deployed in configurations where a client can supply the header. You must be sure that your web server or reverse proxy always sets or strips that header based on the appropriate authentication checks, never permitting an end ... d X-Auth_User (for example) both normalize to the HTTP_X_AUTH_USER key in request.META , you must also check that your web server doesn't allow a spoofed header using underscores in place of dashes. Under WSGI, this warning doesn't apply to RemoteUserM ...
https://man.mtool.work/django/6.1/howto/auth-remote-user.html
REMOTE_USER で認証する — Django 6.1 ドキュメント 8291
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » REMOTE_USER で認証する ¶ This document describes how to make use of external authentication sources in your Django applications. This type of authen ... IS and Integrated Windows Authentication or Apache and mod_authnz_ldap , CAS , WebAuth , mod_auth_sspi , etc. When the web server takes care of authentication it typically provides the authenticated user as REMOTE_USER . In Django, this value is made a ... UserMiddleware must not be deployed in configurations where a client can supply the header. You must be sure that your web server or reverse proxy always sets or strips that header based on the appropriate authentication checks, never permitting an end ... d X-Auth_User (for example) both normalize to the HTTP_X_AUTH_USER key in request.META , you must also check that your web server doesn't allow a spoofed header using underscores in place of dashes. Under WSGI, this warning doesn't apply to RemoteUserM ...
https://man.mtool.work/django/6.1/howto/auth-remote-user.html
Django 4.2.30 release notes — Django 6.1 ドキュメント 7300
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 4.2.30 release notes ¶ April 7, 2026 Django 4.2.30 fixes one security issue with severity "moderate" and four security issues with severity " ... , such a header could be spoofed by supplying a header named with underscores. Under WSGI, it is the responsibility of the server or proxy to avoid ambiguous mappings. (Django's runserver was patched in CVE 2015-0219 .) But under ASGI, there is not the ... rs off; ). Headers containing underscores are now ignored by ASGIRequest , matching the behavior of Daphne , the reference server for ASGI. This issue has severity "low" according to the Django security policy . CVE-2026-4277: Privilege abuse in Generi ... ader according security policy underscores security service memory moderate ASGIRequest hyphens even proxies headers named server Privilege abuse GenericInlineModelAdmin instances forged list editable using クイック検索 Last update: 2026年10月09日 « pr ...
https://man.mtool.work/django/6.1/releases/4.2.30.html
Django 5.2.13 release notes — Django 6.1 ドキュメント 7300
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.13 release notes ¶ April 7, 2026 Django 5.2.13 fixes one security issue with severity "moderate" and four security issues with severity " ... , such a header could be spoofed by supplying a header named with underscores. Under WSGI, it is the responsibility of the server or proxy to avoid ambiguous mappings. (Django's runserver was patched in CVE 2015-0219 .) But under ASGI, there is not the ... rs off; ). Headers containing underscores are now ignored by ASGIRequest , matching the behavior of Daphne , the reference server for ASGI. This issue has severity "low" according to the Django security policy . CVE-2026-4277: Privilege abuse in Generi ... ader according security policy underscores security service memory moderate ASGIRequest hyphens even proxies headers named server Privilege abuse GenericInlineModelAdmin instances forged list editable using クイック検索 Last update: 2026年10月09日 « pr ...
https://man.mtool.work/django/6.1/releases/5.2.13.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT