It's a shame browser makers removed FTP:// browsing support.
FTP was a lot more fun than the homogeneous blob of HTTP we have today. I only discovered FTP transparently via web browsing and clicking around as a kid.
This is another Opiate, Huw Roberts, who was releasing on the (now defunct) Miasmah net label in the early 2000s, but is still running a label called Serein to this today! What a blast from the past... Nice tunes too
With the exception of one comment, which simply restated the link correctly, no one here has pointed out that the URL provided is not in fact served by an FTP server.
Starting a link with http, makes it a WWW link which is expected to be interpreted as HTML, and is served by an WWW server.
An FTP URL would be: ftp://128.237.157.9/pub
Where the leading ftp: designates how the link is to be interpreted. The so called "scheme" of the URL.
In reply to other comments: my browser supports the ftp: scheme without issue.
Ironically, when using the ftp: scheme in the URL, the /pub directory query returns an error: 550 Failed to change directory.
Whereas removing that subdirectory, and just using the scheme and IP address does return the files and subdirectories served by the FTP server (at least the ones with public permissions).
Whereas the http: URL to the same IP and /pub directory does return successfully. With the contents correctly served by the WWW server.
Therefore, this was probably not a great example to use for a post regarding FTP servers. Since the URL http://128.237.157.9/pub is actually served by a WWW server...
Readit News
FTP was a lot more fun than the homogeneous blob of HTTP we have today. I only discovered FTP transparently via web browsing and clicking around as a kid.
Deepest level
http://128.237.157.9/pub/scene.org/music/artists/opiate/opia...
https://www.discogs.com/artist/401-Opiate
Edit: fun, they have my old hippocamp album too :) http://128.237.157.9/pub/scene.org/music/groups/hippocamp/hc...
Starting a link with http, makes it a WWW link which is expected to be interpreted as HTML, and is served by an WWW server.
An FTP URL would be: ftp://128.237.157.9/pub
Where the leading ftp: designates how the link is to be interpreted. The so called "scheme" of the URL.
In reply to other comments: my browser supports the ftp: scheme without issue.
Ironically, when using the ftp: scheme in the URL, the /pub directory query returns an error: 550 Failed to change directory.
Whereas removing that subdirectory, and just using the scheme and IP address does return the files and subdirectories served by the FTP server (at least the ones with public permissions).
Whereas the http: URL to the same IP and /pub directory does return successfully. With the contents correctly served by the WWW server.
Therefore, this was probably not a great example to use for a post regarding FTP servers. Since the URL http://128.237.157.9/pub is actually served by a WWW server...
It's also worth noting, that the http URL: http://128.237.157.9/pub/
Points to the same data as the ftp URL: ftp://128.237.157.9/
While the http URL: http://128.237.157.9/ points to the Carnegie Mellon Computer Club home page.
Dead Comment