AW: [squid-users] Problem with cache_peer_domain

Henrik,
thanks a lot, it works fine.

And this is (hopefully) the final solution:

   cache_peer frd-proxy parent 8080 3130 login=PASS no-query
   cache_peer frd-proxy-nologon parent 8080 3130 login=name:topsecret
no-query

   acl BOE-ELSTER dstdomain 80.146.179.2
   acl BOE-ELSTER dstdomain 80.146.179.3
   acl BOE-ELSTER dstdomain 193.109.238.58
   acl BOE-ELSTER dstdomain 193.109.238.59
   http_access allow BOE-ELSTER
   cache_peer_access frd-proxy-nologon allow BOE-ELSTER
   cache_peer_access frd-proxy-nologon deny all

Hint: frd-proxy and frd-proxy-nologon are the same parent proxy (same IP).

Mit freundlichem Gru�/Yours sincerely
Werner Rost
GMT-FIR - Netzwerk
 
ZF Boge Elastmetall GmbH
Friesdorfer Str. 175, 53175 Bonn, Deutschland/Germany
Telefon/Phone +49 228 3825 - 420
Telefax/Fax +49 228 3825 - 398
werner.rost@zf.com

>-----Urspr�ngliche Nachricht-----
>Von: Henrik Nordstrom [mailto:hno@squid-cache.org]
>Gesendet: Mittwoch, 23. M�rz 2005 12:15
>An: Rost Werner ZFBE GMT-ISN
>Cc: squid-users@squid-cache.org
>Betreff: Re: [squid-users] Problem with cache_peer_domain
>
>
>> cache_peer_domain frd-proxy-nologon BOE-ELSTER
>> cache_peer_domain frd-proxy !BOE-ELSTER
>
>I think you are mixing up cache_peer_domain with
>cache_peer_access... The
>two is similar except that the first takes domain names and the second
>takes acls.
>
>Another note: any ACLs in squid.conf must be defined before
>where they are
>used.
>
>Regards
>Henrik
>
Received on Wed Mar 23 2005 - 05:40:09 MST