Search squid archive

Re: 2.5 ok but 2.6 access denied

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Works just fine for me.

I think it never actually worked for you. A difference between 2.5 and
2.6 is that 2.6 is less keen on retrying requests on errors, where
Squid-2.5 would often ignore the error and go direct. To get back the
old behavior set retry_on_error, but you really should fix the access
rules on that parent..

Regards
Henrik

tor 2006-09-21 klockan 09:09 -0300 skrev HM:
> hello
> 
> is somebody looking at this or is it supposed still not to work on 2.6?
> 
> Hans
> 
> 
> On Tuesday 12 September 2006 12:12, HM wrote:
> > Hi
> >
> > I have on SMP servers more then one squid running.
> >
> > One process as transparent cache  using two or more squid processes as
> > parents (this is on the one server, no external cache parent).
> >
> > The scenario works fine for me with squid 2.5-stable14
> >
> > Now I am trying to upgrade this to 2.6-Stable3
> > I added transparent to the http_port line for the transparent squid process
> > and took the old transparent parameters out
> >
> > all squids are coming up fine
> >
> > but then I get an access denied from the parent caches, nothing goes
> > through.
> >
> > running only one squid transparent it works fine
> >
> > what is the difference between 2.5 and 2.6 that the parents do not accept
> > connections anymore? Any idea here?
> >
> > I run FreeBSD 6.1 amd64
> >
> >
> > Hans
> 

Attachment: signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux