> -----Original Message-----
> From: Gilles Detillieux [SMTP:[EMAIL PROTECTED]]
> Sent: 15 April 1999 19:35
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [htdig3-dev] Use of & as CGI variable separator vs. HTML
> 4.0
>
>
> According to Torsten Neuer:
> > According to Gilles Detillieux:
> > >They also recommend using ";" as an alternate separator, so we should
> > >also handle
> > >
> > >?x=1;y=2
> > >and use this in Display::createURL(), if we're to follow their
> > >recommendations. Does anyone see a problem with using a semicolon in
> > >this manner?
> >
> > I disagree with that since AFAIK a semicolon does not necessarily need
> > to be url-encoded.
> > Could cause trouble if a semicolon is part of a parameter.
>
till now we could not use & as part of a parameter?
> Yeah, if we support the semicolon as a separator, then we'd have to
> url-encode any semicolons withing parameters as a special case. We could
> do likewise with "|" if we chose it as a separator, but we know that it
> may be used quite commonly, so it's best to avoid it.
>
> What I'd like to know is how commonly a ";" appears in input parameters
> to htsearch. If it's very rare, I think it would be worthwhile encoding
> it when it does occur, and using ";" rather than "&" or "&" as a
> variable separator in URLs generated by createURL().
>
>
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
