Hello,
I've searched the archives and received no mojo...
Set-up:
=======
Squid Cache: Version 2.4.STABLE2
We've been using squid and a proxy.pac for a long time, while some
folks use a manual entry pointing all accesses directly at the proxy.
Both browser configurations have worked flawlessly. Until
now. My very simple test proxy.pac currently looks like this:
function FindProxyForURL(url, host)
{
if (isInNet(host, "127.0.0.1", "255.255.255.255") ||
dnsDomainIs(host, ".my.dom") )
return "DIRECT";
else
return "PROXY nnn.nnn.nnn.nn:3128;"
}
Where the IP address matches www-proxy.my.dom.
The Problem:
============
A user complained to me that they were unable to log in to
a LiveLink server when they use the proxy.pac. HOWEVER, if
they use the manual setting, point directly at the proxy server
and port 3128, they can log in.
I have verified this behavior with the above proxy.pac, and the
manual setting.
1. Using proxy.pac (no worky) - there is a CONNECT message in
access.log:
1028835421.884 338 nnn.nnn.nnn.nn TCP_MISS/200 922 CONNECT livelink.some.dom:443 - DIRECT/xxx.xxx.xxx.xxx -
2. Using manual proxy config (which works!) - there is __No__
message in access.log
I'm thinking there is something in my config that I need to tweek,
maybe an ACL or something?
I don't want to include the whole config - but I don't what would
be relevent under these circumstances... If it would be helpful
to provide the ACL settings, or whatever, let me know.
Thanks,
deb
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- There are 10 types of people in the world: those that understand binary, and those that don't. τΏτ ~Received on Thu Aug 08 2002 - 13:51:59 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:09:33 MST