#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
--------------------------------------------------------+-------------------
Changes (by mtredinnick):
* summary: HeadMiddleware - Modify response for HEAD requests => HEAD
processing should be compulsory
* stage: Unreviewed => Accepted
Comment:
Changed title to reflect what is probably the real issue here.
Sorry if you feel I'm mischaracterising what you're saying, arien. That's
obviously not my intention, but we do need to establish what the real
problem is, now that it's veered away from Scott's original wish to add
functionality we already have. It is true that HEAD handling really does
have nothing to with with fix_location_header (which is being used as it
is intended and documented: it fixed the Location header after everything
else is done).
I agree that HEAD handling should probably be compulsory since people
aren't in the habit of throwing an error on methods they don't understand.
We can certainly fix that. If you have an example of something else that
doesn't work that you believe should, again, please post it. It's
difficult to ensure that I've understood all the points you are trying to
raise. As I understand the code at the moment, and thinking through the
possibilities, if you have the !ConditionalGetMiddleware installed, there
should be no HTTP violations occurring. Do you know of a case where that
isn't true? If not, we'll make the HEAD stuff happen by default and that
should fix the main problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/5898#comment:10>
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
-~----------~----~----~----~------~----~------~--~---
