W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2009

Issue 43 (combining fragments)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 28 Jul 2009 12:25:27 +0200
Message-ID: <4A6ED217.5070809@gmx.de>
To: HTTP Working Group <ietf-http-wg@w3.org>
Hi,

looking at <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/43>:

"At present, the behavior in the case where there was a fragment with 
the original URI, e.g.: http://host1.example.com/resource1#fragment1 
where /resource1 redirects to 
http://host2.example.com/resource2#fragment2 is 'fragment1' discarded? 
Do you find fragment2 and then find fragment1 within it? We don't have 
fragment combination rules."

And the proposal:

"Could add note to Location header that combining fragments may have 
unpredictable results."

I just tested this with various browsers.

- Firefox and Safari use the fragment in the location header.

- Opera uses the fragment from the source URI, when present, otherwise 
the fragment from the redirect location

- IE (8) ignores the fragment in the location URI, thus will use the 
fragment from the source URI, when present

Proposal:

"Note: the behavior when fragment identifiers from the original URI and 
the redirect need to be combined is undefined; current User Agents 
indeed differ on what fragment takes precedence."


BR, Julian
Received on Tuesday, 28 July 2009 10:26:12 GMT

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