From: Lennart Borgman <lennart.borgman@gmail.com>
To: Reiner Steib <Reiner.Steib@gmx.de>,
5345@debbugs.gnu.org, Juanma Barranquero <lekktu@gmail.com>
Subject: bug#5345: Password asked when visiting a file in a lightweight checkout
Date: Sun, 10 Jan 2010 18:48:15 +0100 [thread overview]
Message-ID: <e01d8a51001100948x611c312em1054e494e022b7ac@mail.gmail.com> (raw)
In-Reply-To: <87ocl26oet.fsf@marauder.physik.uni-ulm.de>
On Sun, Jan 10, 2010 at 3:10 PM, Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> On Sat, Jan 09 2010, Juanma Barranquero wrote:
>
>> According to RFC 1738 ("Uniform Resource Locators (URL)"),
>> section 3.10 ("FILES"), the syntax is
>>
>> file://<host>/<path>
>>
>> i.e., the slashes are separators. And "[a]s a special case, <host> can
>> be the string "localhost" or the empty string; this is interpreted as
>> `the machine from which the URL is being interpreted'.". So
>> file:///C:/path is a perfectly valid URL for a local file on Windows,
>> as a shorthand for file://localhost/C:/path. I'm surprised Unix URLs
>> for absolute paths do not start with file:////.
>
> I think the RFC assumes that the leading "/" is not part of the
> directory name, so file://<host>/<path> with <host> = localhost and
> <path> = /etc/fstab (etc/fstab relative to /) becomes
> file:///etc/fstab just like /pub/README on ftp.gnu.org is written as
> ftp://ftp.gnu.org/pub/README and not ftp://ftp.gnu.org//pub/README
That sounds like a plausible reading to me. Shouldn't this then mean
that file://c:/some/file.txt is correct, but that
file:///c:/bad/example.txt is wrong?
> ,----[ rfc1738 ]
> | 3.10 FILES
> |
> | The file URL scheme is used to designate files accessible on a
> | particular host computer. This scheme, unlike most other URL schemes,
> | does not designate a resource that is universally accessible over the
> | Internet.
> |
> | A file URL takes the form:
> |
> | file://<host>/<path>
> |
> | where <host> is the fully qualified domain name of the system on
> | which the <path> is accessible, and <path> is a hierarchical
> | directory path of the form <directory>/<directory>/.../<name>.
> `----
>
> Bye, Reiner.
> --
> ,,,
> (o o)
> ---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
>
>
>
>
>
next prev parent reply other threads:[~2010-01-10 17:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f7ccd24b1001091308y34abf466j1424a588134a83e6@mail.gmail.com>
2010-01-09 2:41 ` bug#5345: Password asked when visiting a file in a lightweight checkout Juanma Barranquero
2010-01-09 10:11 ` Michael Albinus
2010-01-09 12:44 ` Juanma Barranquero
2010-01-09 13:52 ` Eli Zaretskii
2010-01-09 14:36 ` Juanma Barranquero
2010-01-09 18:46 ` Dan Nicolaescu
2010-01-09 19:06 ` Juanma Barranquero
2010-01-09 19:20 ` Dan Nicolaescu
2010-01-09 20:08 ` Juanma Barranquero
2010-01-09 20:39 ` Dan Nicolaescu
2010-01-09 20:57 ` Lennart Borgman
2010-01-09 21:04 ` Juanma Barranquero
2010-01-09 21:12 ` Lennart Borgman
2010-01-10 14:10 ` Reiner Steib
2010-01-10 17:48 ` Lennart Borgman [this message]
2010-01-10 19:27 ` Juanma Barranquero
2010-01-10 19:40 ` Lennart Borgman
2010-01-10 20:06 ` Juanma Barranquero
2010-01-10 20:10 ` Lennart Borgman
2010-01-10 20:21 ` Juanma Barranquero
2010-01-10 20:35 ` Lennart Borgman
2010-01-12 18:09 ` Reiner Steib
2010-01-09 21:15 ` Michael Albinus
2010-01-09 21:33 ` Dan Nicolaescu
2010-01-10 6:51 ` Michael Albinus
2010-01-10 17:52 ` Eli Zaretskii
2010-01-10 19:07 ` Michael Albinus
2010-01-09 18:53 ` Michael Albinus
2010-01-09 21:09 ` bug#5345: marked as done (Password asked when visiting a file in a lightweight checkout) Emacs bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e01d8a51001100948x611c312em1054e494e022b7ac@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=5345@debbugs.gnu.org \
--cc=Reiner.Steib@gmx.de \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.