What we've done here is allow transparent proxy, and due to this
redirecting all port 80 proxy traffic to 3128, plus I've redirected 8080
to 3128, for compatability's sake (one of our competitors runs a proxy
on 8080, making my life easier.
Bill Wichers wrote:
>
> Make that three reasons... I have to run some of my client's Squid boxes
> on port 8080 because the client wants to run some piece of "less than
> amazingly well designed" software (like Surf Watch) that thinks that
> proxies should only exist on 8080. Surf Watch, for example, is "100%
> compatible with M$ proxy server", thus you can tell it to use a "proxy
> server" which it automatically interprets as "connections will be going to
> port 8080". When I used port 3128 originally Surf Watch was effectivly
> bypassed (maybe something for everyone to watch out for if their clients
> run Surf Watch), and the only solution I found was to run Squid on port
> 8080.
>
> -Bill
>
> On Sat, 25 Apr 1998, David J N Begley wrote:
>
> > People generally pick 8080 for one of two reasons:
> >
> > - it's a legacy port number (perhaps from something like CERN httpd run
> > as a proxy server) and they can't bear trying to get all their users
> > to change manually configured ports (that's me); or,
> >
> > - other people are doing it, so why shouldn't they do it too?
> >
Received on Sat Apr 25 1998 - 15:28:05 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:39:57 MST