Jason Linhart wrote:
> On 7/19/00 6:42 PM Jeremy Wadsack ([EMAIL PROTECTED]) wrote:
>
> >Incidentally,
> >
> >http://www.ilse.nl/searchresults.dbl?LANGUAGE=NL;profile=st;family=no;sear
> >ch_for=presentatietechnieken;zoeken.x=27;zoeken.y=6;db=web;cacheid=0211290
> >862542;pagnum=1
> >
> >is considere the 'right' way to do CGI scripts, even through (almost)
> >nobody does them that way. This is because the character "&" should be
> >escaped under URL/URI
> >syntax. Therefore Analog should be able to parse a query string that is
> >separated by either ';' or '&'. I'd send a patch Stephen, but I don't know
> >where to find that in your code. :)
>
> I beg to differ. All browsers take multipule fields from a form and
> concatenate them with '&'s. That is the reason that '&' is required to be
> encoded, so that it remains available as a field seperator. Technicaly
> '&' is reserved for special meaning within a particular scheme. The
> special meaning within the HTTP scheme is as a seperator for name value
> pairs in query strings.
>
> >From Netscape's HTML documentation:
>
> A query string consists of a question mark, followed by
> the name/value pairs to be submitted to the program. Each name/value
> pair is separated by an &. Use the URL-encoded value %20 to indicate
> white spaces and %0A to indicate new lines.
>
RFC 1866:
NOTE - The URI from a query form submission can be used in a normal
anchor style hyperlink. Unfortunately, the use of the `&' character
to separate form fields interacts with its use in SGML attribute
values as an entity reference delimiter. For example, the URI
`http://host/?x=1&y=2' must be written `<a
href="http://host/?x=1&y=2"' or `<a
href="http://host/?x=1&y=2">'.
HTTP server implementors, and in particular, CGI implementors are
encouraged to support the use of `;' in place of `&' to save users
the trouble of escaping `&' characters this way.
However, HTML 4.01 Spec says
2. The control names/values are listed in the order they appear in
the document. The name is separated from the value by `=' and
name/value pairs are separated from each other by `&'.
So it appears the world has given up on trying that method, so I stand
corrected regarding what is considered 'right'. I still think that Analog
should parse both, though, since there is historical and empirical evidence
that the ';' standard is in use.
Jeremy Wadsack
Wadsack-Allen Digital Group
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
