Michael Grimm wrote:
Hi,
I am currently using squid 3.0 STABLE19 with the following working config:
access_log /var/log/squid/access.log squid
https_port 443 accel
cert=/etc/ssl/reverse_proxy/server1.mydomain.de.cert
key=/etc/ssl/reverse_proxy/server1.mydomain.de.key
defaultsite=server1.mydomain.de
cache_peer 192.168.1.100 parent 8080 0 originserver no-query
name=server1 forceddomain=server1.mydomain.de
acl reverse_server1 dstdomain server1.mydomain.de
http_access allow reverse_server1
http_access deny all
cache_peer_access server1 allow reverse_server1
cache_peer_access server1 deny all
never_direct allow all
Now I want to integrate a second server running a different web
application in the same config.
The second server should answer over server2.mydomain.de.
I know that there is a vhost functionality in Squid but I just don’t
understand how to use it in this case.
Does this work at all? I could install a second squid for this but
then I would have to use my last precious external IPs (My precious!
:-).
Yes it works. The vhost option will already be handling all the incoming
stuff for you. Just add a second set of cache_peer/cache_peer_access for
the other internal web server with a different ACL naming the other
dstdomain.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.7
Beta testers wanted for 3.2.0.1
