<feed xmlns='http://www.w3.org/2005/Atom'>
<title>django.git/docs/releases/1.11.22.txt, branch main</title>
<subtitle>django
</subtitle>
<id>http://cgit.adnoto.dev/django.git/atom?h=main</id>
<link rel='self' href='http://cgit.adnoto.dev/django.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/'/>
<updated>2019-07-01T05:48:04Z</updated>
<entry>
<title>Fixed CVE-2019-12781 -- Made HttpRequest always trust SECURE_PROXY_SSL_HEADER if set.</title>
<updated>2019-07-01T05:48:04Z</updated>
<author>
<name>Carlton Gibson</name>
<email>carlton.gibson@noumenal.es</email>
</author>
<published>2019-06-13T08:57:29Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=54d0f5e62f54c29a12dd96f44bacd810cbe03ac8'/>
<id>urn:sha1:54d0f5e62f54c29a12dd96f44bacd810cbe03ac8</id>
<content type='text'>
An HTTP request would not be redirected to HTTPS when the
SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings were used if
the proxy connected to Django via HTTPS.

HttpRequest.scheme will now always trust the SECURE_PROXY_SSL_HEADER if
set, rather than falling back to the request scheme when the
SECURE_PROXY_SSL_HEADER did not have the secure value.

Thanks to Gavin Wahl for the report and initial patch suggestion, and
Shai Berger for review.
</content>
</entry>
<entry>
<title>Added stub release notes for security releases.</title>
<updated>2019-07-01T04:57:27Z</updated>
<author>
<name>Mariusz Felisiak</name>
<email>felisiak.mariusz@gmail.com</email>
</author>
<published>2019-06-20T08:45:38Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=30b3ee9d0b33bb440f9c73d1ce9e0e7303887a9f'/>
<id>urn:sha1:30b3ee9d0b33bb440f9c73d1ce9e0e7303887a9f</id>
<content type='text'>
</content>
</entry>
</feed>
