I should've clarified that.
We used the DNS records for AutoDiscovery.
I'm not sure if that matters, but we didn't use DHCP.
Tim Rainier
Information Services, Kalsec, INC
trainier@xxxxxxxxxx
"Rodrigo A B Freire" <zazgyn@xxxxxxxxxxxx>
08/01/2005 08:33 PM
To
<squid-users@xxxxxxxxxxxxxxx>
cc
Subject
Re: proxy.pac
We use both WPAD and PAC... Inclusive, setting the WPAD in DHCP. No
problem at all, no truncated requests in the access.log.
The proxy.pac?Type=WMT is when the Windows Media Player try to open a
web URN.
----- Original Message -----
From: "Kevin" <kkadow@xxxxxxxxx>
To: <trainier@xxxxxxxxxx>
Cc: <squid-users@xxxxxxxxxxxxxxx>
Sent: Monday, August 01, 2005 8:25 PM
Subject: Re: proxy.pac
On 8/1/05, trainier@xxxxxxxxxx <trainier@xxxxxxxxxx> wrote:
> I'd reply to the question sent to the list, but I deleted it already.
>
> There's a bug in IE that truncates the last character of the
> autoconfiguration file.
If I'm reading this right, you're saying that this problem only happens
when using Proxy Automatic Configuration (PAC) in combination with
the automatic discovery feature (WPAD) of MSIE?
> The problem is the packet which requests that file, sometimes get's
> fragmented, not always.
> This essentially causes IE to request two files: proxy.pa and c
> A very simple work-around is to copy proxy.pac to proxy.pa
> You should see somewhat more consistency here.
Interesting. We support many thousands of Windows workstations,
all using proxy.pac but none using WPAD.
I do not see any requests for "proxy.pa" in the logs on the web server
hosting the PAC file. I do see a ton of errors for some really humorous
typos -- it's amazing how many different ways there are to creatively
spell "proxy" :)
Kevin Kadow
(P.S. I do see a high number of requests for "proxy.pac?Type=WMT",
is anybody else seeing these?)
