rejetto forum

Software => HFS ~ HTTP File Server => Topic started by: Anonymous on January 09, 2005, 12:17:31 AM

Title: HTTP vs FTP
Post by: Anonymous on January 09, 2005, 12:17:31 AM
Hey all,

I searched the forums and couldn't find anything (maybe I missed it) but what is the difference between HTTP Servers (like rejetto's) and an FTP server (like Bulletproof FTP)? I have been a long time user of HTTP Server, and it's a great product. I have come across several FTP server products, and I wanted to know the difference between the two.

Thanks in advance!

~Matt
Title: HTTP vs FTP
Post by: Shodan on January 09, 2005, 11:56:01 AM
Its easier to setup as Http. Well regetto made it easy to use. Most companys block FTP protocols. Its probably not the answer you wanted but a more technical person can go into more details.
Title: HTTP vs FTP
Post by: TGeRi on January 09, 2005, 12:16:47 PM
Hi!

FTP is a different protocol. U connect to a HTTP server with a browser (for example IE) and u connect to an ftp server with a special client program
(for ex totalcommander or flashfxp).

The FTP protocol is only used to transfer files (File Transfer Protocol) so i u connect to an ftp u will see only files/folders and u can download then and u wont se a HTML page like in the case on a http server (for exp HFS).

TGeRi

PS: Hope i was clear, sorry for bad english.
PPS: in one word: http serves web pages ftp serves filet to u.
(well almost because http can serv files to u too)
Title: HTTP vs FTP
Post by: rejetto on January 09, 2005, 03:58:10 PM
FTP is a better protocol for file exchange, but HTTP is more wide spread:
anyone has a web browser.
IE is also an ftp client, but i tried to use it and it is terrible unless you are working in LAN.
HTTP is also easier to use in restricted enviroments (firewall, etc)
Title: HTTP vs FTP
Post by: Anonymous on January 09, 2005, 06:25:49 PM
Quote from: "rejetto"
FTP is a better protocol for file exchange, but HTTP is more wide spread:
anyone has a web browser.
IE is also an ftp client, but i tried to use it and it is terrible unless you are working in LAN.
HTTP is also easier to use in restricted enviroments (firewall, etc)

Thanks for clearing that up!