Context Navigation

← Previous Ticket
Next Ticket →

#43 closed design (fixed)

Fragment combination / precedence during redirects

Reported by:	mnot@…	Owned by:	ylafon@…
Priority:	urgent	Milestone:	13
Component:	p2-semantics	Severity:	Active WG Document
Keywords:		Cc:

Description

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.

Attachments (4)

i43.diff (8.5 KB) - added by julian.reschke@… 10 years ago.: Proposed patch for parts 1 & 2.
redir_frag_test.py (6.8 KB) - added by mnot@… 9 years ago.: test script
i43.2.diff (979 bytes) - added by julian.reschke@… 9 years ago.: proposed patch, addressing the TAG input.
i43resolution.diff (2.3 KB) - added by julian.reschke@… 8 years ago.: an attempt to describe the resolution algorithm

Download all attachments as: .zip

Change History (30)

comment:1 Changed 12 years ago by mnot@…

Component set to semantics
Milestone set to unassigned

comment:2 Changed 12 years ago by mnot@…

version set to 00-draft

comment:3 Changed 11 years ago by julian.reschke@…

origin changed from issue 6 to http://lists.w3.org/Archives/Public/ietf-http-wg-old/1999MayAug/0103.html

comment:4 Changed 11 years ago by mnot@…

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

comment:5 Changed 10 years ago by julian.reschke@…

Owner set to julian.reschke@…
Priority set to normal

comment:6 Changed 10 years ago by julian.reschke@…

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."

comment:7 Changed 10 years ago by julian.reschke@…

It appears that IE8 *does* use the fragment idenfitier from Location (the behavior I saw might be limited to localhost).

Thus we seem to have consistent behavior for Safari/IE/Firefox/Chrome (just tested), in that the fragment from the Location header gets used, no matter what the original URI was.

I therefore change my proposal to document *that* as expected behavior.

comment:8 Changed 10 years ago by julian.reschke@…

Milestone changed from unassigned to 08

comment:9 Changed 10 years ago by julian.reschke@…

Milestone changed from 08 to 09
Severity set to Active WG Document

comment:10 Changed 10 years ago by julian.reschke@…

Milestone changed from 09 to 10
Priority changed from normal to urgent

comment:11 Changed 10 years ago by julian.reschke@…

Status changed from new to assigned

Changed 10 years ago by julian.reschke@…

Attachment i43.diff added

Proposed patch for parts 1 & 2.

comment:12 Changed 10 years ago by julian.reschke@…

From [785]:

Allow URI-reference instead of URI in Location; state that there are currently no defined precedence rules for fragment identifiers (relates to #43 and #185)