#25619: Make runserver use HTTP 1.1
-------------------------------+------------------------------------
Reporter: gabn88 | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by timgraham):
* needs_better_patch: 0 => 1
* stage: Ready for checkin => Accepted
Comment:
As noted on the pull request , it looks to me like we'd also need to set
[https://docs.python.org/3.5/library/http.server.html?highlight=protocol_version#http.server.BaseHTTPRequestHandler.protocol_version
WSGIServer.protocol_version]() too. Not sure this is trivial given the
sentence in the Python docs, "If set to 'HTTP/1.1', the server will permit
HTTP persistent connections; however, your server must then include an
accurate Content-Length header (using send_header()) in all of its
responses to clients." Given that, I'd be surprised if older versions of
runserver really used HTTP 1.1.
--
Ticket URL: <https://code.djangoproject.com/ticket/25619#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.5727de20438e454fe8cc9dc8b89bbd49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
