2021-02-01 17:51:16 +08:00
|
|
|
==========================
|
|
|
|
|
Django 3.1.7 release notes
|
|
|
|
|
==========================
|
|
|
|
|
|
2021-02-16 18:14:17 +08:00
|
|
|
*February 19, 2021*
|
2021-02-01 17:51:16 +08:00
|
|
|
|
2021-02-16 18:14:17 +08:00
|
|
|
Django 3.1.7 fixes a security issue and a bug in 3.1.6.
|
|
|
|
|
|
|
|
|
|
CVE-2021-23336: Web cache poisoning via ``django.utils.http.limited_parse_qsl()``
|
|
|
|
|
=================================================================================
|
|
|
|
|
|
|
|
|
|
Django contains a copy of :func:`urllib.parse.parse_qsl` which was added to
|
|
|
|
|
backport some security fixes. A further security fix has been issued recently
|
|
|
|
|
such that ``parse_qsl()`` no longer allows using ``;`` as a query parameter
|
|
|
|
|
separator by default. Django now includes this fix. See :bpo:`42967` for
|
|
|
|
|
further details.
|
2021-02-01 17:51:16 +08:00
|
|
|
|
|
|
|
|
Bugfixes
|
|
|
|
|
========
|
|
|
|
|
|
2021-02-03 04:34:36 +08:00
|
|
|
* Fixed a regression in Django 3.1 that caused ``RuntimeError`` instead of
|
|
|
|
|
connection errors when using only the ``'postgres'`` database
|
|
|
|
|
(:ticket:`32403`).
|
