Django should not send invalid Location headers
|Reported by:||Paul McMillan||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Django's locale middleware currently includes code which generates Location headers with relative URIs.
According to RFC 1945 and 2616, Location headers must be constructed with an absolute URI. While some user agents may support the non-compliant behavior, Django itself should not rely on this, and should generate absolute URIs as it does elsewhere.