2

I have been facing this wierd problem while trying to montor an FTP server. If I try to use ftp://192.x.x.x/home/$USER/output , the monitoring tool fails to pickup the folder. However, if I use ftp://192.x.x.x//home/$USER/output, then the FTP folder is picked up easily. So I want to know, what is the difference between / and // ?

  • Makes one wonder what software is involved. What do you use to monitor and ftp-server is installed? – MadMike Nov 25 '13 at 7:35
  • Monitoring tool is FuseHQ – Ubuntuser Nov 25 '13 at 8:15
  • I couldn't find anything special for your case in the RFC. As far as I understand, this is for the root-hierarchy from within an absolute path. You should be able to add as many slashes there to any URL and always get the same response. – MadMike Nov 25 '13 at 8:21
1

I hope this helps.

A path name consisting of a single slash / resolves to root directory of the process. A path name that begins with two slashes // may be interpreted diffrently, although more than two leading slashes shall be treated as a single slash.

Most implementations simply treat // as / , but may still show // .

Also see UNIX, difference between path starting with '/' and '//'

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.