[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Conversion of special character codes within anchor tags
From: |
Al Gilman |
Subject: |
Re: lynx-dev Conversion of special character codes within anchor tags |
Date: |
Sat, 26 Sep 1998 09:40:54 -0400 (EDT) |
>
> However it is becoming quite common for hard coded forms URLs to use
> ;, partly because it doesn't require entity encoding in the HTML.
>
> > we may both be wrong on this point. RFC 1738 (which is the one I think you
> > want, states in section 3.3:
> >
> > "Within the <path> and <searchpart> components, "/", ";", "?" are
> > reserved."
> >
> > So ";" is not available as a delimiter.
That is taking the "reserved" status backward. Here "reserved"
means you can't use it for anything _but_ a delimiter. It is
worth reading RFC 2396 on this point.
>
> It is definitely being used as that these days although I don't know the
> underpinning standards.
>
>
Re: lynx-dev Conversion of special character codes within anchor tags, David Woolley, 1998/09/26