Re: Squid, Wingate and name resolution !?

Hello,

Thank you Robert for your answer...

> two things:
>
> 1) As far as I recall, wingate's caching mechanism does not read
> content-expiry headers, or last-modified dats in http data, it just keeps
> the page local for x days. You may want to put squid in front of wingate,
if
> that is possible. In fact you can probably do everything you want with
unix
> tools.
I wish we use 2 Squid proxies but I can't decide so far. Maybe latter.

> 2) for DNS, configure squid to use the wingate machine as a dns server,
and
> configure wingate to do DNS proxying. (It may be on by default). either
edit
> your /etc/resolv.conf, or your squid.conf to only list the wingate
machine.

I finally added the following lines to squid.conf and it works fine...

        cache_peer 192.168.0.1 parent 80 0 no-query default
        acl all src 0.0.0.0/0.0.0.0
        never_direct allow all

Laurent

>
> ----- Original Message -----
> From: "Laurent Derrien" <derrien.smai@gouv.nc>
> To: <squid-users@ircache.net>
> Sent: Wednesday, August 02, 2000 8:51 AM
> Subject: Squid, Wingate and name resolution !?
>
>
> > Hello,
> > I try to configure a Squid proxy in a private network and I want it to
use
> a
> > Wingate proxy to access Internet.
> > So, the Squid proxy is a child of the Wingate proxy. It is working with
IP
> > addresses (HTTP requests get answers), but the name resolution fails.
> > I would like Squid relies on Wingate for name resolution, but I don't
know
> > if it is possible.
> > Thank you for any advice.
> >
> > Laurent Derrien
> > derrien.smai@gouv.nc
> >
> >
>
Received on Tue Aug 01 2000 - 23:00:16 MDT