#35051: HEAD Responses Drop Headers
---------------------------------+------------------------------------
Reporter: Paul Bailey | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 5.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Paul Bailey):
The discussion linked is over Content-Length being returned for the body
of the HEAD response, so this is always "Content-Length: 0" which doesn't
match the GET request.
The easiest thing to do at the time was to just remove Content-Length
since it is not required. However, for HTTP Range Requests Content-Length
is required.
So I think the proper thing to do is to allow it if Content-Length is not
Zero. If the header is not 0 then that means it was set by the user and
should be allowed through.
--
Ticket URL: <https://code.djangoproject.com/ticket/35051#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018c84312072-fdc27825-a143-4405-b622-d857d06b5ad3-000000%40eu-central-1.amazonses.com.
