This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author orf
Recipients martin.panter, orf
Date 2017-07-31.23:19:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501543162.05.0.318681605673.issue31076@psf.upfronthosting.co.za>
In-reply-to
Content
Django recently switched to HTTP 1.1 on their development server, and it works fine as long as the middleware is included that generates the content length. Using a 'bare' Django project with no middleware the server will just hang.

It sounds like the easiest fix is to disable keepalive support in the development server, which sounds like a reasonable fix (it doesn't have that much benefit locally I think?).

It was certainly surprising to find this issue, I know it is documented but that could certainly be improved. It's currently just a plain line of text in quite a text-heavy page, perhaps it should be put in a warning box?
History
Date User Action Args
2017-07-31 23:19:22orfsetrecipients: + orf, martin.panter
2017-07-31 23:19:22orfsetmessageid: <1501543162.05.0.318681605673.issue31076@psf.upfronthosting.co.za>
2017-07-31 23:19:22orflinkissue31076 messages
2017-07-31 23:19:21orfcreate