Re: [squid-users] Forwarding of errors

Hi Matthias,

The configuration of our servers is the same as yours. The problem I
found was that the internal cache was configured to go direct on certain
items. This created what I believe was the same problem you are
describing.

To overcome this what I did was to set the following two options:

always_direct deny all
never_direct allow all

The description of what the options do is in the configuration file,
however I can't recall if they are available in the version you are
running.

BTW, I tried the URL you provided and I found it works fine in our
environment. (SQUID 2.5STABLE1 on Solaris 2.6)

David

Matthias Weigel wrote:
>
> Hi,
>
> the problem is i have to go through the upstream ("external") proxy.
> And of course:
> - Why does squid drop the page with errorcode and create a new one with an error that
> is just not there.
> - Why does squid do this when fetching from an upstream proxy, but does it not when
> fetchin directly?
>
> Best Regards
>
> Matthias Weigel
> ISOnova GmbH
>
> David Beards schrieb:
>
> > You do also need to check always_direct to make sure that it is not
> > being told to go direct for certain things.
> >
> > David Beards
> > CFA
> > Technical Manager Networks and Systems
> > 4 Lakeside Drive
> > Burwood East, Victoria, Australia
> >
> > Robert Collins wrote:
> > >
> > > On Thu, 2002-10-31 at 02:32, Matthias Weigel wrote:
> > > > Hi, Robert,
> > > >
> > > > unfortunately allways_direct cannot be used, because the "internal" squid can
> > > > only communicate to the "external" because of firewall restrictions.
> > >
> > > Heh. What was I on? I *meant* never_direct. never_direct is what you
> > > need.
> > >
> > > Sorry,
> > > Rob
> > >
> > > ------------------------------------------------------------------------
> > > Name: signature.asc
> > > signature.asc Type: application/pgp-signature
> > > Description: This is a digitally signed message part
Received on Thu Oct 31 2002 - 03:26:17 MST