Hello,
I'm trying to direct requests for a particular urls to an
internal proxy, but squid always tries to go direct. I'm running squid
2.1PATCH1 on htt://ika:8080, while the proxy I'm aiming at is
imeproxy.tibco.com.
My squid.conf contains:
cache_peer imeproxy.tibco.com parent 8080 7 no-query no-digest no-netdb-exchange
Then I tried both:
cache_peer_domain imeproxy.tibco.com .ime.reuters.com
and then:
acl reuters-dstdomain dstdomain ime.reuters.com
cache_peer_access imeproxy.tibco.com allow reuters-dstdomain
and finally:
acl reuters-regex url_regex ime.reuters.com
cache_peer_access imeproxy.tibco.com allow reuters-regex
The url I'm trying to reach is:
If I try going directly to the proxy it works:
GET -p "http://imeproxy.tibco.com:8080" http://www.ime.reuters.com
However, the following does not work:
GET -p "http://ika:8080" http://www.ime.reuters.com
I turned up the debugging, an found this in cache.log:
1999/01/09 12:44:14| aclMatchAclList: checking reuters-regex
1999/01/09 12:44:14| aclMatchAcl: checking 'acl reuters-regexurl_regex ime.reuters.com'
1999/01/09 12:44:14| aclMatchRegex: checking 'http://www.ime.reuters.com/'
1999/01/09 12:44:14| aclMatchRegex: looking for 'ime.reuters.com'
1999/01/09 12:44:14| aclMatchAclList: returning 1
1999/01/09 12:44:14| neighborsCount: 0
1999/01/09 12:44:14| peerSelectIcpPing: counted 0 neighbors
1999/01/09 12:44:14| peerSelectFoo: After peerSelectIcpPing.
1999/01/09 12:44:14| whichPeer: from 0.0.0.0 port 0
1999/01/09 12:44:14| whichPeer: from 0.0.0.0 port 0
1999/01/09 12:44:14| whichPeer: from 0.0.0.0 port 0
1999/01/09 12:44:14| peerSelect: DIRECT/www.ime.reuters.com
So it looks like its matching the regex, but then not selecting the
proxy.
Any ideas?
Thanks,
Andy
Received on Fri Jan 08 1999 - 21:02:02 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:43:56 MST