- From: David Norris <kg9ae@geocities.com>
- Date: Wed, 24 Nov 1999 13:19:21 -0500
- To: <MDenny@owners.com>
- Cc: "Piers Williams" <PiersW@zinc.co.uk>, <www-html@w3.org>
> I was surprised that I could not find a
> specification within the HTML RFC's
> for what to do when you have a fragment
> identifier AND a querystring
URIs are not specified by HTML. URIs are specified by RFC 2396:
"Uniform Resource Identifiers (URI)" A reference to
http://www.ics.uci.edu/pub/ietf/uri/rfc2396.txt was posted somewhere
in the thread.
> > 1) mypage.asp?myvar=value#myfragment
> > 2) mypage.asp#myfragment?myvar=value
> IMHO the first makes more sence (and it's what O'Reilly quote in
their
As per RFC2396 section 2.4.3, these characters are
delimiters and not allowed within a URI:
delims = "<" | ">" | "#" | "%" | <">
< > and " are used to delimit a URI from surrounding text (e.g.
<http://somewhere/> or "http://somewhere/"). % delimits an escape
sequence. And, # denotes a fragment which itself is not part of the
actual URI.
Thus:
> mypage.asp?myvar=value#myfragment
Means:
URI: mypage.asp?myvar=value
Fragment: myfragment
And:
> mypage.asp#myfragment?myvar=value
Means:
URI: mypage.asp
Fragment: myfragment?myvar=value
--
,David Norris
The OpenSA Project - http://www.opensa.de/
Dave's Web - http://www.webaugur.com/dave/
ICQ Universal Internet Number - 412039
E-Mail - dave@webaugur.com
Received on Wednesday, 24 November 1999 13:22:02 UTC