#5898: HEAD processing should be compulsory
--------------------------------------------------------+-------------------
Reporter: Scott Barr <[EMAIL PROTECTED]> | Owner: nobody
Status: reopened | Component:
HTTP handling
Version: SVN | Resolution:
Keywords: | Stage:
Accepted
Has_patch: 1 | Needs_docs:
0
Needs_tests: 0 | Needs_better_patch:
0
--------------------------------------------------------+-------------------
Comment (by arien <[EMAIL PROTECTED]>):
mtredinnick, the patches are independent.
What I'm aiming for is in
[http://code.djangoproject.com/attachment/ticket/5898/http_requirements.diff
the last patch]. It makes responses to HEAD requests correct independent
of the middlewares in use. It goes beyond this in that it also removes
content for responses that can't have any content (because of their status
code), (re)setting the Content-Length header to match.
The patch also created one single point for response fix-ups and moves the
call to fix_location_header there, because both it fix_location_header and
remove_unallowed_response_content make sure Django always plays by some
basic HTTP rules in what it emits.
--
Ticket URL: <http://code.djangoproject.com/ticket/5898#comment:12>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
