Re: [squid-users] Virtual hosts + 127.0.0.1 problems

Just like in the Apache configuration you should tell Squid to bind to a
specific address. See the http_port directive.

But your problem is a misunderstanding on what "httpd_accel_host virtual"
means. This directive is for supporting IP based virtual hosts, not domain
based virtual hosts. For domain based virtual hosts see the
httpd_accel_uses_host_header directive, and make sure Squid knows that all
your domains are on 127.0.0.1.. (or use httpd_accel_single_host on).

Regards
Henrik

David Brown wrote:
> I'm trying to run a virtual host server, with Squid 2.4 (in Accelerator
> mode) and Apache 1.3.
>
> I want to bind Apache to port 80, so that I don't get those annoying :81
> or
>
> :8080 URLs
>
> If I define this in my squid.conf:
>
> http_port 80
> httpd_accel_host 127.0.0.1
> httpd_accel_port 80
>
> and this in my apache.conf
>
> Port 80
> BindAddress 127.0.0.1
>
> That works fine and dandy.. BUT... unfortunately I'm running virtual hosts
> and I need to know what domain the request is for .. so I need to use this
> instead:
>
> httpd_accel_host virtual.
>
> But when I do this, I get these errors: "WARNING: Forwarding loop detected
> for....."
>
> This kinda makes sense, because rather than sending the request to
> 127.0.0.1:80 (under the previous configuration), the request goes back to
> domain-name.com:80 and get's caught again by Squid rather than Apache..
>
> How can I run virtual hosts, yet bind Apache to port 80 ?
>
> Does this make sense ?
>
> TIA

-- 
Basic free Squid support provided thanks to MARA Systems AB
Your source of advanced reverse proxy solutions or customized
Squid solutions. http://www.marasystems.com/products/