Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
What about legacy client software lacking sftp support?
Who still uses FTP, for anything?
Posted Jul 7, 2011 7:25 UTC (Thu) by rqosa (subscriber, #24136)
> What about anonymous FTP?
Assuming that the anonymous users aren't allowed to upload files, HTTP should be a suitable replacement.
Posted Jul 7, 2011 10:35 UTC (Thu) by anselm (subscriber, #2796)
Kinda, sorta as long as you don't rely on FTP features such as partial downloads, wildcard-filename downloads or translation of line endings for text files.
Of course there are ways of getting these sorted on an HTTP server, but they may involve added inconvenience for the downloading user or the server operator. For example, an FTP server will give you a directory listing but an HTTP server usually won't (not as long as you don't enable it explicitly, and then usually in an HTML format that programs must laboriously parse).
Posted Jul 7, 2011 12:04 UTC (Thu) by Jonno (subscriber, #49613)
The closest thing to a standard there is is "do like POSIX `ls -la`", but that is not universally followed, especially by ftp servers on non-POSIX hosts...
For HTTP there is at least webdav, which can provide a standardized machine parseable directory listing...
Posted Jul 8, 2011 7:53 UTC (Fri) by rqosa (subscriber, #24136)
> partial downloads
HTTP supports that, by way of the "Range:" request header.
> translation of line endings for text files
That really shouldn't be necessary anymore, since many programs (text editors, etc.) support the multiple different line-ending types. (And of course it will corrupt binary files if turned on by mistake.)
Posted Jul 8, 2011 8:02 UTC (Fri) by rqosa (subscriber, #24136)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds