Re: Squid multiple ports

From: Graham Toal <>
Date: Tue, 6 May 1997 11:22:46 -0500 (CDT)

> From: Cefiar <>

> On Tue, 6 May 1997, David Richards wrote:
> > What advantage would I have, or for what purpose would I choose to
> > implement the patch that enables squid to listen on different ports??
> >
> > Why would this help me??
> This is useful if...
> 1> You are migrating from one cache product to another. You can add a
> 'different' port of 8080, and it'll take all requests on 8080, which is
> the default in apache if you enable the proxy module.
> 2> It can give you freedom to play with other cache programs by simply
> disabling squid's use of a port, and telling your new cache program to use
> that port only. eg: I could use the port duplication module and give ftp
> it's own port number. I can then disable it later in squid, and run a
> dedicated ftp cache that supports ftp and http requests, without any of
> the users really realising that any change had occured.

I'm running two caches one one machine; one a straight forward squid cache;
the other a CERN cache acting as a proxy only, which rewrites some URLs
so that schoolkids can't access the playboy page etc. I'd like that
second cache to be an instance of squid too, using the squid redirector,
so this multi-port stuff would probably do the trick. However I'd prefer
not to slow down accesses for everyone else by having them also use
the redirector, albeit as a no-op. (It would have to check the browser
IP address first; it's easier if it just knows it's a school from the
different port number).

With this multi-port patch, is there an easy way to choose a different
redirector according to the port number the request came in on?


PS I don't have the ram to run two copies of squid independently, as
far as I understand it. Or is it possible to do a proxy-only squid
that doesn't eat ram like the main one?
Received on Tue May 06 1997 - 14:35:47 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:35:07 MST