Re: [squid-users] Pseudo-random 403 Forbidden...

2008-07-07 Thread John Doe
Hi again... I don't know what happened (if I changed something or if I wrongfuly thought it was fixed) but the siblings are not talking anymore... at all. :( No error message, no denied... So let's start from the begining... configure --prefix=$PREFIX \ --enable-time-hack \ --enable-underscores

Re: [squid-users] Pseudo-random 403 Forbidden...

2008-07-07 Thread John Doe
> > In other words please file a bug report at http://bugs.squid-cache.org/ > > I filed Bug 2403. As advised, I turned via back on and it fixed the problem. Thx a lot Henrik, JD

Re: [squid-users] Pseudo-random 403 Forbidden...

2008-07-03 Thread John Doe
> > > > > > Looks like a false positive. > > > > > > For info, if I remove the digests, everything works fine... > > > > Cache digests has a higher false positives rate than ICP, but it can > > happen with ICP as well. I checked with no digests again and there is an odd behavior. If by example:

Re: [squid-users] Pseudo-random 403 Forbidden...

2008-07-02 Thread Henrik Nordstrom
On ons, 2008-07-02 at 18:49 +0200, Henrik Nordstrom wrote: > On ons, 2008-07-02 at 08:21 -0700, John Doe wrote: > > > > > Looks like a false positive. > > > > For info, if I remove the digests, everything works fine... > > Cache digests has a higher false positives rate than ICP, but it can > hap

Re: [squid-users] Pseudo-random 403 Forbidden...

2008-07-02 Thread Henrik Nordstrom
On ons, 2008-07-02 at 08:21 -0700, John Doe wrote: > > > > Looks like a false positive. > > For info, if I remove the digests, everything works fine... Cache digests has a higher false positives rate than ICP, but it can happen with ICP as well. Regards Henrik signature.asc Description: This i

Re: [squid-users] Pseudo-random 403 Forbidden...

2008-07-02 Thread John Doe
> > > Looks like a false positive. For info, if I remove the digests, everything works fine...

[squid-users] Pseudo-random 403 Forbidden...

2008-07-02 Thread John Doe
> > Looks like a false positive. > > > > Maybe you need to enable retry_on_error. Shouldn't be needed, but I > > haven't verified this in quite a while.. > > It only changed the "403 Forbiden" to constant "200 No headers, assuming > HTTP/0.9" > > > > 'The "latest" from a CentOS 5.2: squid-2.6.S