This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: [Fwd: %20 in href attribute]
- From: "Julian Reschke" <julian dot reschke at gmx dot de>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 23 Jan 2002 17:53:04 +0100
- Subject: RE: [xsl] [Fwd: %20 in href attribute]
- Reply-to: xsl-list at lists dot mulberrytech dot com
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Thomas B.
> Passin
> Sent: Wednesday, January 23, 2002 5:43 PM
> To: xsl-list@lists.mulberrytech.com
> Subject: Re: [xsl] [Fwd: %20 in href attribute]
>
>
> [Julian Reschke]
>
> [ Thomas B. Passin]
> > > Sent: Tuesday, January 22, 2002 10:27 PM
> > > ...
> > >
> > > If you have a server that responds to a url with a space, and does not
> > > respond to the same url with the space replaced by "%20", that
> > > server has a
> > > bug.
> >
> > The server will never see it, because it's in the fragment part
> of the URI
> > reference.
> >
> >
>
> Are you saying that the browser removes the fragment before
> sending the url
Yes.
> to the server? I can see how that would work, but rfc 2396 says that
> fragments are to be escaped like the other parts of urls. Does
I agree.
> that make it
> a browser error if it doesn't url-decode a fragment?
I would think so.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list