Shane Curcuru/CAM/Lotus wrote:
> Did you try any other variations on the exact URL for the file? I think to
> be a legal absolute file: URL you need at least two slashes separating the
> scheme file:// from the path portion (or three, I always forget).
We recently needed to clarify the file: URLs for Cocoon. The changes
are not yet on the website, but here is the snippet ...
-----
File: URLs
<p>
In your sitemaps you may need to refer to some resource that is outside
the webapp context (e.g. UNIX /foo/bar/this.xsl
e.g. Windows C:\foo\bar\this.xsl). You need to use the file: convention
with the following syntax for absolute filesystem pathnames.
</p>
<ul>
<li>UNIX ... <code>file:///foo/bar/this.xsl</code></li>
<li>Windows ... <code>file:///C:/foo/bar/this.xsl</code></li>
</ul>
<p>
Everything starting with a URI scheme identifer like file:
or http: is an absolute URI. An absolute file URL is
<code>file://some.host/some/path/to/file.ext</code>
... the host can be omitted, defaulting to localhost, so you can write
<code>file:///some/path/to/file.ext</code>
</p>
<p>
Further information is at RFC2396:
<link href="http://www.rfc-editor.org/rfc/rfc2396.txt";>Uniform Resource
Identifiers (URI): Generic Syntax</link>
</p>
</s1>
------
