p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[3.1.x] Fixed some formatting issues in docs. 

Backport of 803e70b1ad from master
This commit is contained in:
Mariusz Felisiak 2020-05-27 09:07:02 +02:00
parent df88f24b1f
commit ebf553397a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ref/checks.txt
View File

@ -146,7 +146,7 @@ If you're using MySQL or MariaDB, the following checks will be performed:
``max_length`` > 255. *This check was changed to* ``mysql.W003`` *in Django ``max_length`` > 255. *This check was changed to* ``mysql.W003`` *in Django
3.1 as the real maximum size depends on many factors.* 3.1 as the real maximum size depends on many factors.*
* **mysql.W002**: MySQL/MariaDB Strict Mode is not set for database connection * **mysql.W002**: MySQL/MariaDB Strict Mode is not set for database connection
'<alias>'. See also :ref:`mysql-sql-mode`. ``<alias>``. See also :ref:`mysql-sql-mode`.
* **mysql.W003**: MySQL/MariaDB may not allow unique ``CharField``\s to have a * **mysql.W003**: MySQL/MariaDB may not allow unique ``CharField``\s to have a
``max_length`` > 255. ``max_length`` > 255.
@ -413,8 +413,8 @@ The following checks are run if you use the :option:`check --deploy` option:
set to ``True``, so your pages will not be served with an set to ``True``, so your pages will not be served with an
``'X-XSS-Protection: 1; mode=block'`` header. You should consider enabling ``'X-XSS-Protection: 1; mode=block'`` header. You should consider enabling
this header to activate the browser's XSS filtering and help prevent XSS this header to activate the browser's XSS filtering and help prevent XSS
attacks. *This check is removed in Django 3.0 as the ``X-XSS-Protection`` attacks. *This check is removed in Django 3.0 as the* ``X-XSS-Protection``
header is no longer honored by modern browsers.* *header is no longer honored by modern browsers.*
* **security.W008**: Your :setting:`SECURE_SSL_REDIRECT` setting is not set to * **security.W008**: Your :setting:`SECURE_SSL_REDIRECT` setting is not set to
``True``. Unless your site should be available over both SSL and non-SSL ``True``. Unless your site should be available over both SSL and non-SSL
connections, you may want to either set this setting to ``True`` or configure connections, you may want to either set this setting to ``True`` or configure

2
docs/topics/async.txt
View File

@ -62,7 +62,7 @@ If you want to use these, you will need to deploy Django using
<async-middleware>` contexts. Some of Django's middleware is built like <async-middleware>` contexts. Some of Django's middleware is built like
this, but not all. To see what middleware Django has to adapt, you can turn this, but not all. To see what middleware Django has to adapt, you can turn
on debug logging for the ``django.request`` logger and look for log on debug logging for the ``django.request`` logger and look for log
messages about *`"Synchronous middleware ... adapted"*. messages about *"Synchronous middleware ... adapted"*.
In both ASGI and WSGI mode, you can still safely use asynchronous support to In both ASGI and WSGI mode, you can still safely use asynchronous support to
run code in parallel rather than serially. This is especially handy when run code in parallel rather than serially. This is especially handy when