After reading all the comments, I now completely agree that Django is doing the right thing and it falls onto the user to do sanity checking.
Always helps to have another set of eyes, so thank you to everyone who took time to post their thoughts! Cal On Tue, Dec 6, 2011 at 7:54 AM, Paul McMillan <p...@mcmillan.ws> wrote: > As Ian said, Django does the right thing here according to my tests > too, and generates the absolute URIs required by RFC 2616. If you've > figured out some way to actually get location headers that are > noncompliant, that would be a bug, but the handling of // is correct. > > -Paul > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
