Henrik Nordstrom wrote:
>
> Joe Cooper wrote:
>
> > Why? For this very reason, of course! ;-) If there is no redirection,
> > then the port 80 traffic will always hit Squid. With the redirection
> > it's possible to skip over it for some packets. Without it, Squid just
> > sits there sucking up everything on port 80. (And it's not an option to
> > redirect that traffic to another port...because then what? The origin
> > web server wants the traffic on 80 and doesn't listen anywhere else.)
>
> Well.. it does not actually matter which port Squid listens to. You
> still need a redirection or the TCP stack won't accept the traffic and
> instead tries to forward it to the real destination.
>
> It works equally well using port 80 as port 3128, or 49765 for that
> matters. No functional difference there.
>
> There is one difference in that not runnig Suqid on port 80 allows you
> to run a web server on port 80 on the same machine..
You're right, I stand corrected. I guess I knew that. That's what I
get for staying up so late and still trying to answer questions. (I
knew there was some reason I always left it on 3128...and it's so Apache
can be run also.)
Thanks for the clarification Henrik.
--
Joe Cooper <joe@swelltech.com>
Affordable Web Caching Proxy Appliances
http://www.swelltech.com
-- To unsubscribe, see http://www.squid-cache.org/mailing-lists.htmlReceived on Wed Aug 23 2000 - 13:08:57 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:55:04 MST