文件Uri方案和相关文件

假定uri的方案是“文件”。还假设路径以“。”开头。

示例路径为“ ./.bashrc”。fulluri看起来如何？'file：//./..bashrc'对我来说似乎很奇怪。

简而言之，文件URL的形式为：

file://localhost/absolute/path/to/file [ok]

或者，您可以省略主机（但不能省略斜线）：

file:///absolute/path/to/file [ok]

但不是这个：

file://file_at_current_dir [no way]

也不是这样：

file://./file_at_current_dir [no way]

我刚刚通过Python的urllib2.urlopen（）确认

来自http://en.wikipedia.org/wiki/File_URI_scheme的更多详细信息：

"file:///foo.txt" is okay, while "file://foo.txt" is not,
although some interpreters manage to handle the latter

不可能使用完整文件：带有'。'的URI。或路径中没有根部分的“ ..”段。无论您使用“ file：//./..bashrc”还是“ file：///....bashrc”，这些路径都没有意义。如果要使用相对链接，请在没有协议/权限部分的情况下使用它：

<a href="./.bashrc">link</a>

如果要使用完整的URI，则必须告诉相对根，您的相对路径是：

<a href="file:///home/kindrik/./.bashrc">link</a>

根据RFC 3986

The path segments "." and "..", also known as dot-segments, are
defined for relative reference within the path name hierarchy.  They
are intended for use at the beginning of a relative-path reference
(Section 4.2) to indicate relative position within the hierarchical
tree of names.  This is similar to their role within some operating
systems' file directory structures to indicate the current directory
and parent directory, respectively.  However, unlike in a file
system, these dot-segments are only interpreted within the URI path
hierarchy and are removed as part of the resolution process (Section
5.2).

The complete path segments "." and ".." are intended only for use
within relative references (Section 4.1) and are removed as part of
the reference resolution process (Section 5.2).  However, some
deployed implementations incorrectly assume that reference resolution
is not necessary when the reference is already a URI and thus fail to
remove dot-segments when they occur in non-relative paths.  URI
normalizers should remove dot-segments by applying the
remove_dot_segments algorithm to the path, as described in Section 5.2.4.

The complete path segments "." and ".." are intended only for use
within relative references (Section 4.1) and are removed as part of
the reference resolution process (Section 5.2) 

RFC 3986甚至描述了删除这些“”的算法。和URI中的“ ..”。

在终端中，可以使用“ $ PWD”键入“ file：//$PWD/.bashrc”以引用当前目录。

您不应在之后加上双斜线file:。正确的形式是

'file:.bashrc'

参见RFC 3986，path-rootless定义

我不知道您的用例。

我的节点代码中也有类似的需求，因此当我需要相对于我的工作目录的文件url时，我会像这样创建一个url ...

const url = "file://" + process.cwd() + "/" + ".bashrc";

在unix shell脚本中，我设法做到了：

file://`pwd`/relative-path

在您的特定情况下：

file://`pwd`/.bashrc