On Tue, 2003-07-08 at 09:56, Bruno Dumon wrote: > On Mon, 2003-07-07 at 22:55, Nathaniel Alfred wrote: > > The latest version of excalibur.source.SourceResolver packaged > > with Cocoon-2.1m3 normalizes URIs containing "/foo/../bar" to "/bar". > > At first sight this looks a good idea and is according to RFC 2396. > > > > But when dealing with file: URIs foo can be a symbolic link > > (aka short-cut) such as "foo -> some/where/else". Following > > filesystem semantics, "/foo/../bar" results in "/some/where/bar". > > Used with care this can be a powerful feature, which got lost now. > > (My setup is currently royally screwed due to that.) > > > > So is file:/foo/../bar going to stay a URI as per RFC 2396, or shall > > we have an exception to suppress the "<segment>/.." normalization > > step for file:. > > Technically it's no problem to restore the previous behaviour for the > file: scheme. I didn't think of the above use case. I'll look into > fixing it and let you now when it's done.
Ah, I see you have already a patch submitted to Avalon... -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
