W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2011

Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects

From: Cameron Heavon-Jones <cmhjones@gmail.com>
Date: Wed, 14 Dec 2011 17:35:47 +0000
Cc: Mark Nottingham <mnot@mnot.net>, Willy Tarreau <w@1wt.eu>, "Roy T. Fielding" <fielding@gbiv.com>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
Message-Id: <AAFEC756-0BE7-43C1-9790-8EA6EE9907E9@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>

On 14/12/2011, at 5:13 PM, Julian Reschke wrote:

> On 2011-12-14 18:04, Cameron Heavon-Jones wrote:
>> ...
>> I don't think it makes a difference, a response should be parsed irrespective of the request although i don't know that this is definitively the case.
>> 
>> I just checked Firefox and the same behaviour is seen, i would assume the same from the other browsers but i can do more tests to confirm.
>> ...
> 
> What exactly did you check?
> 
> I'm VERY sure that browsers automatically follow a 302 + Location upon page navigation, no matter whether there's a payload or not.
> 
> Best regards, Julian


I setup the same form i used testing POST to encode into URI instead of form params and sent as GET. It produced a URI like this:

http://localhost:8090/web/test/it?status=302&location=http%3A%2F%2Fwww.example.com&content=on


The response was the same as for POST, ie:

HTTP/1.1 302 Found
Location        http://www.example.com
Content-Type    text/html
Content-Length  199
Server          Jetty(6.1.7)
				
<html>
    <body>
        <h1>Response</h1>
        <p>Response Status: 302</p>
        <p>Response Reason: Found</p>
    </body>
</html>


I don't think there's anything else?

Thanks,
Cam
Received on Wednesday, 14 December 2011 17:36:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:51 GMT