#27379: Django violates RFC7230 when handling requests.
-------------------------------------+-------------------------------------
Reporter: Stavros | Owner: nobody
Korokithakis |
Type: Bug | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Florian Apolloner):
Oh, I found something interesting in (
https://tools.ietf.org/html/rfc7230#section-5.3.2 ):
{{{
To allow for transition to the absolute-form for all requests in some
future version of HTTP, a server MUST accept the absolute-form in
requests, even though HTTP/1.1 clients will only send them in
requests to proxies.
}}}
That said, now that HTTP/2 exists and is the successor of 1.1, we should
look what that spec requires. Either way, I think Django should not
concern itself to much with it, since it is not a server but just a
library rejecting an invalid request.
Arguably there is actually a bug, ie if a client sends:
{{{
GET http://valid.com/ HTTP/1.1
Host: alsovalid.com
}}}
but I cannot figure out a sane reason to do this :D
--
Ticket URL: <https://code.djangoproject.com/ticket/27379#comment:5>
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/071.8913213d0e55fa01fbbebeab162f7e94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
