Re: Proxy server policy [was Re: gated]
- To: firstname.lastname@example.org
- Subject: Re: Proxy server policy [was Re: gated]
- From: email@example.com (Charles Briscoe-Smith)
- Date: 10 Dec 1997 13:34:27 -0000
- Message-id: <firstname.lastname@example.org>
- References: <19971208203942.56861@wyvern> <Pine.LNX.3.96.971209113548.720Aemail@example.com>
In article <Pine.LNX.3.96.971209113548.720Afirstname.lastname@example.org>,
Jason Gunthorpe <email@example.com> wrote:
>Well, http is pretty simple, it's either authenticated or unauthenticated
>HTTP proxy protocol. There should be a way to specifiy for which hosts it
>applies to.. You could also do HTTP over socks4/5 but that's a bit silly.
>FTP is difficult, there is at least:
> ftp over http
> ftp over user@host
> ftp over site
> ftp over ?? [I forget this one]
> ftp over NAT (passive)
> ftp over socks4 and socks5
>Many of those have authenticated versions as well and all should have a
>way to specify which addresses apply.
We have an ftp cache here which seems to be accessed differently from
any of these (unless I misunderstood you). You ftp to the cache,
login anonymously, and cd to a particular directory. So to get to
...and so on. I'm not sure that you can ever have a scheme that will work
for -all- the wierd and wonderful proxies, caches and firewalls out there.
(This cache is something that was knocked up locally, I think. It's
integrated with the HENSA mirrors, but fetches updates to individual
files on demand, too.)
White pages entry, with PGP key: <URL:http://alethea.ukc.ac.uk/wp?95cpb4>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .