Opened 15 years ago
Closed 12 years ago
#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)
Change History (30)
comment:1 Changed 15 years ago by mnot@…
- Component set to semantics
- Milestone set to unassigned
comment:2 Changed 15 years ago by mnot@…
- version set to 00-draft
comment:3 Changed 15 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 14 years ago by mnot@…
comment:5 Changed 14 years ago by julian.reschke@…
- Owner set to julian.reschke@…
- Priority set to normal
comment:6 Changed 14 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 14 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 14 years ago by julian.reschke@…
- Milestone changed from unassigned to 08
comment:9 Changed 13 years ago by julian.reschke@…
- Milestone changed from 08 to 09
- Severity set to Active WG Document
comment:10 Changed 13 years ago by julian.reschke@…
- Milestone changed from 09 to 10
- Priority changed from normal to urgent
comment:11 Changed 13 years ago by julian.reschke@…
- Status changed from new to assigned
comment:12 Changed 13 years ago by julian.reschke@…
comment:13 Changed 13 years ago by julian.reschke@…
Note that the test cases mentioned above are broken; see http://lists.w3.org/Archives/Public/ietf-http-wg/2010JanMar/0265.html. Need to re-investigate this.
comment:14 Changed 13 years ago by julian.reschke@…
Updated tests and test results: http://lists.w3.org/Archives/Public/ietf-http-wg/2010JanMar/0275.html
comment:15 Changed 13 years ago by julian.reschke@…
comment:16 Changed 13 years ago by mnot@…
The remaining question is: do we want to define it, or do we believe this depends on the media type?
comment:17 Changed 13 years ago by mnot@…
I quickly re-tested the latest browsers:
IE9p3: all passed Safari 5 (OSX): fails T4, T8 FF 3.6.6: all passed Chrome 5.0.375.99: all passed Opera 10.60: fails T3, T7
comment:18 Changed 13 years ago by mnot@…
Let's try that with a bit of formatting:
- IE9p3: all passed
- Safari 5 (OSX): fails T4, T8
- FF 3.6.6: all passed
- Chrome 5.0.375.99: all passed
- Opera 10.60: fails T3, T7
comment:19 Changed 13 years ago by julian.reschke@…
- Milestone changed from 10 to 11
- Owner changed from julian.reschke@… to ylafon@…
- Status changed from assigned to new
comment:20 Changed 13 years ago by mnot@…
- Milestone changed from 11 to unassigned
comment:21 Changed 12 years ago by julian.reschke@…
Feedback from W3C TAG: http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0504.html
comment:22 Changed 12 years ago by julian.reschke@…
comment:23 Changed 12 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from new to closed
comment:24 Changed 12 years ago by mnot@…
- Milestone changed from unassigned to 13
comment:25 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:26 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Could add note to Location header that combining fragments may have unpredictable results.