[squid-users] Re: Re: Re: Big trouble

From: Bert Moorthaemer <[email protected]>
Date: Wed, 15 Nov 2006 18:12:26 +0100

Henrik,

"Bert Moorthaemer" <bert.moorthaemer@blumex.com> wrote in message
news:ejf5ji$d0l$1@sea.gmane.org...
> Henrik,
>
>>> >> I use Squid2.6STABLE5 as a proxy to access DMZ located webservers
>>> >> from
>>> >> the
>>> >> outside and also as a HTTP proxy for my internal clients. But there
>>> >> is a
>>> >> problem: I get forward loops on my external interface. I tried all
>>> >> kind
>>> >> of
>>> >> different setup's, but it doesn't make any difference.
>>>
>>> It's monday now (well tuesday to be correct :-)) and I tried to
>>> circumvent
>>> the problem by bypassing ICAP, but
>>> that doesn't make a difference .. any other thoughts?
>
>>Any always_direct directives involved?
> No
>
>>Using any redirectors?
> Yes, I use squidGuard
>
>>The external http_port, is it configured using the vhost directive or
>>just defaultsite?
> Both
>
>>What does access.log say?
> Can't tell you right now because I disabled the acceleration to internal
> servers
>
>>What does cache.log say?
> Can't tell you right now because I disabled the acceleration to internal
> servers
>
> What I can tell you though ... I use IPFW and I have a "fwd 127.0.0.1,3128
> from any to any 80" and that seems to work on outbound connections, but
> what I can remember from cache.log is that it loops on my internal
> interface on port 80 for internal connections . Should I add a rule saying
> "fwd 127.0.0.1 from any to any 80" also???
>

I think I am going to try a different path: Apache as reverse proxy ...
let's see what that brings OR do you have anything comments on my previous
post?

Regards,

Bert.
Received on Wed Nov 15 2006 - 10:13:42 MST

This archive was generated by hypermail pre-2.1.9 : Fri Dec 01 2006 - 12:00:03 MST