Just to share a little more of the weirdness (discovered while reading a couple of the historical URL & URI RFCs several days ago): Per the original spec, in FTP URLs, - ftp://example.net/foo/bar will get you bar inside the foo directory inside the default directory of the FTP server at example.net ( i.e. CWD foo, RETR bar); - ftp://example.net//foo/bar will get you bar inside the foo directory inside the empty strin…
From source code of preferred ftp/http client, maybe this is helpful. Also suggest reading source code for djb's ftp server. Parse URL of form (per RFC 3986): ://[ [: ]@] [: ][/ ] XXX: this is not totally RFC 3986 compliant; will have the leading `/' unless it's an ftp:// URL, as this makes things easier for file:// and http:// URLs. ftp:// URLs have the `/' between the host and the URL-path removed, but any addition…
Re: URLs: It's Complicated
#41ffff