RE: [xsl] Ampersand for URLs

[Robert Seber <robert.seber@xxxxxxxxxxxxxxxxxx>]

The conversion 

& --> & is done by the browser

%26 --> & is done by the server

> -----Original Message-----
> From: Thomas B. Passin [mailto:tpassin@xxxxxxxxxxxx]
> Sent: Friday, April 20, 2001 6:27 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] Ampersand for URLs
> 
> 
> I always understood that the url string was to be unescaped before any
> further processing was done on it.  If so, the %26 would be 
> restored to "&"
> and so would still function as a separator.  I have to admit 
> that I didn't
> try it, though.
> 
> Cheers,
> 
> Tom P
> 
> Robert Seber said
> 
> > I think that you've missed the point - the ampersand is required to
> seperate
> > out the parameters - not as part of the value of a 
> parameter.  You'd use
> %26
> > if you wanted to pass through an ampersand as a value, but not for
> > delimiting the parameters.
> >
> > e.g.
> >
> > /pub.asp?meal=roast&pub=dog%20%26%20duck
> >
> > would be used to pass through parameters meal and pub with 
> values "roast"
> > and "dog & duck"
> 
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list