Re: Support for relative URL in Location header

2013-11-05 Thread Maxim Dounin
Hello! On Tue, Nov 05, 2013 at 08:30:42AM -0800, Jeroen Ooms wrote: > On Mon, Nov 4, 2013 at 5:08 PM, Maxim Dounin wrote: > > The proxy_redirect directive does string replacement, not URI > > mapping. If you want it to replace "/two/" with "/one/", you can > > configure it to do so. It's just

Re: Support for relative URL in Location header

2013-11-05 Thread Jeroen Ooms
On Mon, Nov 4, 2013 at 5:08 PM, Maxim Dounin wrote: > The proxy_redirect directive does string replacement, not URI > mapping. If you want it to replace "/two/" with "/one/", you can > configure it to do so. It's just not something it does by > default. Exactly. I was trying to argue that it pr

Re: Support for relative URL in Location header

2013-11-04 Thread Maxim Dounin
Hello! On Mon, Nov 04, 2013 at 10:42:00AM -0800, Jeroen Ooms wrote: > HTTP status codes such as 201, 301, 302, etc rely on the HTTP Location > header. The current standard of HTTP specifies that this URL must be > absolute. However, all popular browsers will accept a relative URL, > and it is cor

Support for relative URL in Location header

2013-11-04 Thread Jeroen Ooms
HTTP status codes such as 201, 301, 302, etc rely on the HTTP Location header. The current standard of HTTP specifies that this URL must be absolute. However, all popular browsers will accept a relative URL, and it is correct according to the upcoming revision of HTTP/1.1. See also [1]. I noticed