Re: [squid-users] Squid + non standard ports behind firewall

Well.. start by reading squid.conf.default.

It is a normal ACL driven directive. For requests that is allowed Squid
will never attempt going directly, enforcing the use of peers.

The opposite is always_direct. Forces Squid to go direct to the site no
matter what.

In between (neither never_direct or always_direct is allowed), Squid
makes up it's own mind on if it is best to use a peer or go direct.

--
Henrik Nordstrom
Squid Hacker
"Beukers, W.J." wrote:
> 
> Hai,
> 
> eeeuh, where can i find more info about this never_direct directive ? the
> search on the web site gives nothing.....
> 
> thx!
> 
> -----Oorspronkelijk bericht-----
> Van: Henrik Nordstrom [mailto:hno@squid-cache.org]
> Verzonden: dinsdag 18 september 2001 9:07
> Aan: Barry Darnton
> CC: 'squid-users@squid-cache.org'
> Onderwerp: Re: [squid-users] Squid + non standard ports behind firewall
> 
> Barry Darnton wrote:
> 
> > If I just connect to a site on say 8080 it hands of to the firewall on
> > port 80 (it's parent) without any error, but if the site has a
> > username and password required then after entering the details, squid
> > then tries to communicate direct with the destination on the non
> > standard port. Of course the firewall gets upset with this as it is
> > not running a proxy on this port.
> 
> Have you told Squid it is inside a firewall?
> 
> see the never_direct directive.
> 
> --
> Henrik Nordstrom
> Squid Hacker