#987: HttpResponseRedirect uses/allows relative URIs for the HTTP Location
header, which is forbidden by HTTP
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Core framework
Version: | Resolution:
Keywords: | Stage: Design decision
needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------+-----------------------------------------
Changes (by Ludvig Ericson <[EMAIL PROTECTED]>):
* cc: [EMAIL PROTECTED] (added)
Comment:
Sorry if I'm being blatantly ignorant, but kind sires, can we not simply
try to find the HTTP Host header, which is in fact mandatory in HTTP 1.1,
and most HTTP 1.0 clients send it anyway? If it doesn't exist, then the
client leaves us no choice but to violate the HTTP RFCs. Not entirely sure
how this would be done with Django, but the concept is there.
On a slightly related note, I don't get why you need absolute URLs, what
bothers me most is the fact that you have to specify the protocol (scheme
if you will) - makes it even harder as we have to specify HTTP vs. HTTPS.
+add self to Cc
--
Ticket URL: <http://code.djangoproject.com/ticket/987#comment:17>
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
-~----------~----~----~----~------~----~------~--~---
