On Tue, Feb 25, 2003 at 04:47:26PM +0100, Ard van Breemen wrote:
And telnet localhost 9090 works?
And if so:
GET http://www.porn.com/ HTTP/1.0
empty line
The parent proxy daemon serving port 9090 ist temporarily down thus
causing a dead parent. It is perfectly okay that squid refuses to use
On Fri, Feb 21, 2003 at 03:35:38PM +0100, Christoph Haas wrote:
This is what I get told in the cache.log when the parent goes down:
2003/02/21 15:25:38| The request GET http://www.porn.com/ is ALLOWED,
because it matched 'all'
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
On Fri, Feb 21, 2003 at 06:58:41PM +0100, Henrik Nordstrom wrote:
And you are absolutely sure you configured Squid with prefer_direct
off?
Definitely! I even stopped and started the squid service instead of
doing squid -k reconfig. What log file or config file can I provide?
I'm a bit
And you are absolutely sure you configured Squid with prefer_direct
off?
Regards
Henrik
fre 2003-02-21 klockan 15.35 skrev Christoph Haas:
Henrik, thanks for your patience.
Then your Squid is probably not happy about your parents for one reason
or another. Usually this is seen on an
Hi, folks...
We want to use a proxy chain consisting of Squid and another proxy
server on the same host. The user asks squid:3128 and the request is
being forwarded to the only configured parent proxy:
cache_peer localhost parent 9090 0 no-query
My [always|never]_direct settings are:
If you want Squid to go direct then you cannot use never_direct..
See also prefer_direct.
Regards
Henrik
On Thursday 20 February 2003 19.35, Christoph Haas wrote:
Hi, folks...
We want to use a proxy chain consisting of Squid and another proxy
server on the same host. The user asks
Henrik, thanks for replying.
On Thu, Feb 20, 2003 at 09:29:38PM +0100, Henrik Nordstrom wrote:
If you want Squid to go direct then you cannot use never_direct..
See also prefer_direct.
I have tried various combinations of never_direct and always_direct. In
fact I never really understood why
