#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 marfire):
* cc: k@… (added)
Comment:
This issue bit me recently because Chrome refuses to use ETags if the
server responds with `HTTP/1.0` (see
[[http://stackoverflow.com/a/28033770/2395796|here]], which I can
confirm). That led to some frustrating debugging.
So +1 to fixing this and #5897.
--
Ticket URL: <https://code.djangoproject.com/ticket/25619#comment:9>
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.a55b9d5d852d9a4e16f38e7207cdcdae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
