6 ms·
> The web is gradually consuming all that came before it. It's about cost, too. HTTP can be cached very efficiently, but FTP not at all. If I were the operator
by mschuster91 10y ago
> The web is gradually consuming all that came before it.
It's about cost, too. HTTP can be cached very efficiently, but FTP not at all. If I were the operator in charge and I had the choice between next-to-free caching by nearly anything, be it a Squid proxy, apt-cache or nexus, or no caching and having to maintain expensive servers, I'd choose HTTP.
- agumonkey 10y agoWhat we need if FTP over HTTP.
- astrodust 10y agoWhat about Gopher? Will nobody think of Gopher?
- badsectoracula 10y agoActually i thought about Gopher (i even have my own client - http://runtimeterror.com/tools/gopher/ http://runtimeterror.com/tools/gopher/ - although it only does text) since it basically behaves as FTP++ with abstract names (sadly most modern gopherholes treat it as hypertext lite by abusing the information nodes). Gopher generally avoids most of FTP's pitfalls and it is dead easy to implement.
- kevin_thibedeau 10y agoAt least there's still Jigdo.
- dmoreno 10y agoAs a side note, there was a nice podcast about Gopher a few days ago at Techstuff [1] [1] http://shows.howstuffworks.com/techstuff/what-was-gopher.htm http://shows.howstuffworks.com/techstuff/what-was-gopher.htm
- mschuster91 10y agoWell, there is WebDAV. At least Windows and OS X support it (Windows from Explorer, OS X from Finder), no idea about mainstream Linux/Android/iOS support though. Also, no idea if WebDAV can deal with Unix or Windows permissions, but I did not have that problem when I set up a WebDAV server a year ago. IIRC WebDAV uses GET for retrieval, so the read parts can be cached by an intermediate proxy and the write part be relayed to the server.
- donatj 10y agoAs someone who once tried to write a WebDAV server I cannot with good convince recommend it. It's Bizarre extended HTTP protocol that should not exist.
- mschuster91 10y agoOut of curiosity: why did you try to write your own WebDAV server? Apache ships a pretty much works-OOTB implementation - the only thing I never managed to get working was to assign uploaded files the UID/GID of the user who authenticated via HTTP auth to an LDAP server.
- donatj 10y agoMore specifically a CalDAV server which is a bizarre extension of WebDAV that shouldn't exist. We wanted one to connect to our internal identity server. That project was abandoned.
- carussell 10y agoRelated: "I Hope WebDAV Dies"[1] 1. https://news.ycombinator.com/item?id=10213657 https://news.ycombinator.com/item?id=10213657
- eikenberry 10y agoLinux has great webdav support with the fuse filesystem, davfs. I used it with my box.net account and it worked fine. http://savannah.nongnu.org/projects/davfs2 http://savannah.nongnu.org/projects/davfs2
- astrodust 10y agoExactly. You can offload HTTP to anyone, an HTTP proxy is absolutely trivial to set up, and an HTTP cache is even easier. FTP is not nearly as trivial, plus it's a stupid, broken protocol that deserves to die. The whole thing is a giant bag of hurt.
- mschuster91 10y ago> FTP is not nearly as trivial, plus it's a stupid, broken protocol that deserves to die. I agree with you, but FTP has one very valid use case left: easy file sharing, especially for shared hosting. FTP clients are native to every popular OS, from Android to Windows (only exceptions I know are Win Mobile and iOS), and there's a lot of ecosystem built around FTP. There is SCP and SFTP but they don't really have any kind of widespread usage in the non-professional world.
- astrodust 10y ago> [Has] one very valid use case left: easy file sharing, especially for shared hosting. Nope. Nope. Nope. Not easy. Not secure. Not user friendly. Not anything good. Have an iPhone and need to FTP something? Don't have installation rights on your Windows workstation and need to FTP something? Unpleasant if not confusing as all hell. Dropbox or a Dropbox-like program is significantly easier to get people on board with. Any "ecosystem" built around FTP is rotten to the core. Blow it up and get rid of it as soon as you can. Some vendors insist on using FTP because reasons, but those reasons are always laziness. I can't be the only one that would prefer they use ssh/scp/rsync with actual keys so I can be certain the entity uploading a file is actually them and not some random dude who sniffed the plain-text password off the wire.
- Spooky23 10y agoHuh? Windows explorer has FTP built into the shell. As does every other desktop OS. If you care about file integrity, you want to out of band to verify the signatures on the binary anyway. Dropbox is blocked in most commercial networks and offers no assurance of anything.
- mato 10y ago> It's about cost, too. HTTP can be cached very efficiently, but FTP not at all. It's ironic that you mention cost and caching but lot of services used for software distribution of one kind of another (e.g. Github releases) are following the "HTTPS everywhere" mantra and HTTPS can't be cached anywhere other than at the client.
- calpaterson 10y agoGithub probably trust their CDN with their TLS key. For Debian, packages are secured by PGP in combination with checksums so it's not relevant for them. The debian repos are often HTTP only.
- mschuster91 10y ago> and HTTPS can't be cached anywhere other than at the client. No. Nexus for example can certainly cache apt, as well as Squid can do if you provision it with a certificate that's trusted by the client. Also, Cloudflare supports HTTPS caching if you supply them with the certificate, and if you pay them enough and host some special server that handles the initial crypto handshake you don't even have to hand over your cert/privkey to them (e.g. required by law for banks, healthcare stuff etc)
- mato 10y agoTo clarify; what I meant is that HTTPS can't be cached by third parties. If I want to run a local cache of anything served over HTTP it's as easy as spinning up a Squid instance. With resources served over HTTPS I can't do that.