2 Oct
2012
2 Oct
'12
5:41 a.m.
Imho ftp is a pita with firewalls in place. That's why any protocol that sticks to
just one port and initIation direction for communication is nice.
-----Original Message-----
From: Mouse <mouse at rodents-montreal.org>
Sender: cctalk-bounces at classiccmp.orgDate: Mon, 1 Oct 2012 23:29:26
To: <cctalk at classiccmp.org>
Reply-To: "General Discussion: On-Topic and Off-Topic Posts"
<cctalk at classiccmp.org>
Subject: Re: Webservers,
apache and not. [Re: strange remark about your collection?]
>> I don't recall why I initially started
running [bozohttpd on my
>> anon FTP area]; the most plausible reason I can think of offhand is
>> to shut up people who were whining about having to (horrors!) use
>> something other than a Web browser to look at my stuff.
> I've been using a web browser to transfer files from anonymous FTP
> sites for years, as have many others. Why didn't they just use an
> ftp:// URL?
I don't know. Perhaps they were behind firewalling that allowed HTTP
but not FTP. Perhaps it was one of the (few) people I know that don't
really understand such things and had human-layer trouble with non-http
URL methods. Perhaps the browser in question was a so crippled as to
not support ftp://. More likely than any of those, I suspect, is that
the actual reason was something else and my guess was completely wrong.
It _was_ years and years ago.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B