Hacker News new | ask | show | jobs
by kbeckmann 3679 days ago
While on the subject, what is the difference between file:/path/to/file and file:///path/to/file ? Usually I only see the latter being used.
1 comments
vermilingua 3679 days ago
In file:///, the file:// part signifies the protocol (think http://) and the / in /path/to/file signifies the root directory (think / in /home/user/)

I have never seen file:/ used before, so I can't really comment, but it seems invalid to me (and browsers auto-redirect it to ///).

link
jameshart 3679 days ago
Almost.

The file: signifies the protocol. The /// is actually //<machinename>/ with an empty machinename as a shorthand for 'localhost'.

link
MoSal 3679 days ago
Interesting.

Why is this interpreted as a relative path?

     cd /etc
     curl file://resolv.conf
link
throwanem 3679 days ago
Well, it's ill-formed, so what the UA does with it isn't really specified; cURL presumably treats it as a path relative to . because that's what the developer(s) decided that cURL should do. (For comparison, Firefox transforms it into file:///resolv.conf, then tries to find /resolv.conf on localhost and fails.)
link