No,
http://example.com/\data\file.xsl/../foo.xsl
That is _not_ how the URI RFC defines how a relative URI is made
given a base URI of x and a relative URI of Y you do not make
x/../y
you _have_ to remove from x any characters after the last / and then
append y.
If the current URI is
http://example.com/\data\file.xsl
and a local URI is
foo.xsl
then it is the _client_ that has to put these together and make an
absolute uri to get from the server, the client doesn't know what kind
of machine the server is it just follows the uri spec and that is
absolutely clear, the absolute uri corresponding to the relative uri is
http://example.com/foo.xsl
David
--
http://www.dcarlisle.demon.co.uk/matthew
________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list