Re: Extended URL for frames

Jon Degenhardt (jrd@netcom.com)
Sun, 15 Sep 1996 21:55:20 -0700


Date: Sun, 15 Sep 1996 21:55:20 -0700
From: jrd@netcom.com (Jon Degenhardt)
Message-Id: <199609160455.VAA00798@netcom.netcom.com>
To: jrd@netcom.com
CC: connolly@w3.org, davidp@earthlink.net, www-html@w3.org, www-style@w3.org
In-reply-to: <199609152002.NAA03057@netcom.netcom.com> (jrd@netcom.com)
Subject: Re: Extended URL for frames

My apologies. RFC1808 specifies left-right parsing to find the fragment id.

--Jon

I wrote:
> Daniel W. Connolly <connolly@w3.org> writes:
>> Hmmm... I'm pretty sure I've seen implementations that scan
>> from the right for the first #, and consider that to be the
>> split between the URL and the fragment identifier.
>
> This is the first step in the parsing algorithm described in RFC 1808,
> "Relative Uniform Resource Locators" (http://www.w3.org/pub/WWW/
> Addressing/rfc1808.txt).