简言之,URL文件采取下列形式:

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

or you can omit the host (but not the slash):

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

但这并不是:

file://file_at_current_dir [no way]

否则:

file://./file_at_current_dir [no way]

我刚刚证实,通过Sald 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有,有,有,有的放矢,没有这条道路的根基。 您是否使用文件http://./.bashrc或文档http:///.bashrc。 这些道路将毫无意义。 如果你想要使用一种相对联系,则不用礼宾/授权部分使用:

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

如果你想充分利用国际独立人士协会,你必须说明你相对的道路是:

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

http://www.rfc-editor.org/rfc/rfc3986“rel=“nofollow noreferer” 题目=“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甚至描述了消除这些“......”和“......”的算法。

在一个终点站,你可以使用“PWD”的“笔记:笔记”。

You should not put double slash after file:. Correct form is

 file:.bashrc 

见RFC 3986 。 定义

URIs一向是绝对的(除非是它们相对URIs,而URI是另一个没有图形的分支)。 这是因为它们是一种服务器-客户技术,在这种技术中,参照服务器的工作名录并不有意义。 那么,在服务器-客户情况下,参考文档系统是否毫无意义? 然而,RFC 80 只允许绝对途径:

file:file.txt
file:./file.txt