Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

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

Browse Source 
Backport of 803e70b1adb71d86eb5bbb4074ef5ff96ae6e55d from master.
This commit is contained in:
Mariusz Felisiak 2020-05-27 09:07:02 +02:00
parent f175e03fc2
commit 24cffddc6f
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ref/checks.txt
View File

@ -123,7 +123,7 @@ If you're using MySQL, the following checks will be performed:
* **mysql.E001**: MySQL does not allow unique ``CharField``\s to have a
``max_length`` > 255.
* **mysql.W002**: MySQL Strict Mode is not set for database connection
'<alias>'. See also :ref:`mysql-sql-mode`.
``<alias>``. See also :ref:`mysql-sql-mode`.
Model fields
------------
@ -373,8 +373,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
``'X-XSS-Protection: 1; mode=block'`` header. You should consider enabling
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``
header is no longer honored by modern browsers.*
attacks. *This check is removed in Django 3.0 as the* ``X-XSS-Protection``
*header is no longer honored by modern browsers.*
* **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
connections, you may want to either set this setting to ``True`` or configure