Re: [BUG] wwwoffle misinterprets # symbol in 'Location' header
Maxim Kirillov <[email protected]>
| Newsgroups | gmane.network.wwwoffle.user |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Sep 21, 2005 at 07:14:53PM +0100, Andrew M. Bishop wrote: > Max Kirillov <max630-JGs/[email protected]> writes: >> HTTP/1.1 302 >> Location: <URL>#<fragment> >> >> and wwwofle performs the 'wwwofle -fetch' command, it >> recursively requests document <URL>%23<fragment> instead >> of <URL> > > It is not defined in HTTP specification to have a header > with a fragment identifier. <...> The HTTP protocol does > not handle fragment identifiers anywhere, it is only > browsers that understand what they are and they are only > valid for HTML type documents. Let's look further: http://www.w3.org/TR/html4/struct/links.html#edef-A: --------------------- href = URI [->http://www.w3.org/TR/html4/types.html#type-uri] --------------------- http://www.w3.org/TR/html4/types.html#type-uri: --------------------- This specification uses the term URI as defined in [URI] (see also [RFC1630]). --------------------- The [URI] link leads to RFC2396, wich explicitly says that "As such, it [fragment] is not part of a URI, but is often used in conjunction with a URI." So, we can state that href arrtibute cannot contain fragment also. But this is absurdly. I tend to think that this is a flaw in standards. So, there is no reason for this flaw not to appear in other places, including the HTTP specification. -- Maxim Kirillov Plesk Developer SWsoft, Inc.