934acf1126
Ticket #25619 changed the default protocol to HTTP/1.1 but did not properly implement keep-alive. As a "fix" keep-alive was disabled in ticket #28440 to prevent clients from hanging (they expect the server to send more data if the connection is not closed and there is no content length set). The combination of those two fixes resulted in yet another problem: HTTP/1.1 by default allows a client to assume that keep-alive is supported unless the server disables it via 'Connection: close' -- see RFC2616 8.1.2.1 for details on persistent connection negotiation. Now if the client receives a response from Django without 'Connection: close' and immediately sends a new request (on the same tcp connection) before our server closes the tcp connection, it will error out at some point because the connection does get closed a few milli seconds later. This patch fixes the mentioned issues by always sending 'Connection: close' if we cannot determine a content length. The code is inefficient in the sense that it does not allow for persistent connections when chunked responses are used, but that should not really cause any problems (Django does not generate those) and it only affects the development server anyways. Refs #25619, #28440.
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. Thanks for checking it out.
All documentation is in the "docs" directory and online
at https://docs.djangoproject.com/en/stable/.
If you're just getting started, here's how we recommend you read the
docs:
- First, read
docs/intro/install.txtfor instructions on installing Django. - Next, work through the tutorials in order
(
docs/intro/tutorial01.txt,docs/intro/tutorial02.txt, etc.). - If you want to set up an actual deployment server, read
docs/howto/deployment/index.txtfor instructions. - You'll probably want to read through the topical guides (in
docs/topics) next; from there you can jump to the HOWTOs (indocs/howto) for specific problems, and check out the reference (docs/ref) for gory details. - See
docs/READMEfor instructions on building an HTML version of the docs.
Docs are updated rigorously. If you find any problems in the docs, or think they should be clarified in any way, please take 30 seconds to fill out a ticket here: https://code.djangoproject.com/newticket
To get more help:
- Join the
#djangochannel on irc.freenode.net. Lots of helpful people hang out there. Read the archives at https://botbot.me/freenode/django/. See https://en.wikipedia.org/wiki/Wikipedia:IRC/Tutorial if you're new to IRC. - Join the django-users mailing list, or read the archives, at https://groups.google.com/group/django-users.
To contribute to Django:
- Check out https://docs.djangoproject.com/en/dev/internals/contributing/ for information about getting involved.
To run Django's test suite:
- Follow the instructions in the "Unit tests" section of
docs/internals/contributing/writing-code/unit-tests.txt, published online at https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/unit-tests/#running-the-unit-tests