5 ms·
> With HTTP it's not as easy. Activate directory listing and `wget --recursive`.
by majewsky 9y ago
> With HTTP it's not as easy.
Activate directory listing and `wget --recursive`.
- 1_2__4 9y agoDid you not read the parent comment? Not everyone works for a tech-savvy Silicon Valley company where people just breezily swap out it tech every few months.
- Piskvorrr 9y agoEvery few months? It seems weird, but HTTP and FTP are approximately the same age: 20-something.
- ars 9y agoThat hardly does the same thing. You get the directory listing files stored, which you don't want. You don't get file permissions transferred. There are issues with .dot files. Worse, you have to secure your server to make sure .php files in someone's home directory don't accidentally get run. By default a web server will run files - unless you specially configure it not to, FTP never does that. It's a LOT harder to secure it with HTTP. And if you have places where you want stuff run, and other places where you want files transferred? It's possible, but your likelihood of making a mistake in the configuration is very very high. HTTP is really not suited for bulk file transfer. SFTP works though.
- vthriller 9y ago> By default a web server will run files - unless you specially configure it not to You can't really run anything using default nginx configuration, and even after some tweaking, you still need some FastCGI/WSGI/whatever-compliant daemon to pair it with to be able to "run something". Same goes for `python -m http.server`, except you basically cannot make it execute anything at all.