- From: Henrik Nordstrom <henrik@henriknordstrom.net>
- Date: Tue, 28 Jul 2009 17:32:20 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
tis 2009-07-28 klockan 12:25 +0200 skrev Julian Reschke: > 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 we don't allow fragments in Location or Content-Location either, with both referencing absoluteURI and not URI-reference. Neither 2068, 2396 or 3986 (in the form of absolute-URI) allows fragments in this production. So imho it's sufficient to just say that the behavior is unspecified if you return any other forms of URIs including those with fragments, if anything at all needs to be said on the subject. Regards Henrik
Received on Tuesday, 28 July 2009 15:32:56 UTC