Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion HTTP vs. FTP

Received: by 10.68.73.229 with SMTP id o5mr12893203pbv.7.1328589949391;
        Mon, 06 Feb 2012 20:45:49 -0800 (PST)
Path: lh20ni269254pbb.0!nntp.google.com!news1.google.com!goblin3!goblin.stu.neva.ru!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!cs.uu.nl!news.stack.nl!aioe.org!.POSTED!not-for-mail
From: Ivan Shmakov <oneing...@gmail.com>
Newsgroups: gnu.misc.discuss,comp.protocols.tcp-ip
Subject: HTTP vs. FTP
Followup-To: comp.protocols.tcp-ip
Date: Tue, 07 Feb 2012 11:45:35 +0700
Organization: Aioe.org NNTP Server
Lines: 34
Message-ID: <86wr7zfdzk.fsf@gray.siamics.net>
References: <32018575.1261.1328335352218.JavaMail.geo-discussion-forums@prhz38>
NNTP-Posting-Host: FtDGZaUx6k7Bzdiv4MgYAg.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
X-Notice: Filtered by postfilter v. 0.8.2
Cancel-Lock: sha1:X3Q9Qyt76ratghrI2XiNBcX3m78=
Content-Type: text/plain; charset=us-ascii

>>>>> principalkec  <principal...@gmail.com> writes:

	[Cc: news:comp.protocols.tcp-ip.]

 > Here is a new anonymous ftp server for many of your freesoftware
 > downloads.

 > ftp://infinity.kmeacollege.ac.in

	Apparently, it's also an HTTP server:

http://infinity.kmeacollege.ac.in/

	The FTP protocol, whose current specification (RFC 959 [1]) was
	published back in October 1985, is long time obsolete for most
	common purposes.  It lacks many conveniences of the
	now-ubiquitous HTTP protocol (like proper MIME type encoding and
	unambiguous time stamps), while having several idiosyncrasies of
	its own, like having three (!) data transmission modes, and
	using separate connections for command and data transfer, thus
	demanding for explicit support from routers doing transport
	(port) address translation (variously known as NAT or PAT.)

	It's not uncommon for HTTP proxies to support the FTP protocol
	as well.  It means that there're FTP users that actually use
	HTTP clients to communicate to FTP servers.  Such a protocol
	conversion is, however, prone to errors, since the target FTP
	server and the HTTP proxy may be configured to support
	different, and incomparable, data transmission modes.

[1] http://tools.ietf.org/html/rfc959

-- 
FSF associate member #7257