Hello, I have local web server publication on 80 port with redirection to https protocol for local and external clients. And TMG refuses to serve real "/wpad.dat" to clients instead it serves blank html.

Now I created web publish rule with same Web Listener on 80 port on Internal network that redirects any request with path "/wpad.da*", but while this rule works for "/wpad.dad" and "/wpad.dat?" it doesn't work for "/wpad.dat"! Why?

I also created simply rule to block access to local "/wpad.dat" url, but it doesn't work either while web listener on next rule is active TMG still returns blank html.

And when new rules are disabled request to published server for "/wpad.dat" on http protocol returns blank html while it should redirect to https and forward request to real server according to rule configuration. However, request on https is forwarded to published server.

My configuration requires local web server publication and distribution of wpad.dat file on 80 port, only workaround that i see is to make new server that will redirect requests to wpad.dat file to alternate url.

Thank you for advice on my problem.

Hi,

Thank you for the post.

Please refer to this guide to deploy WPAD: http://technet.microsoft.com/en-us/library/bb794779.aspx.

Regards,

WPAD is configured properly and proper file is served if web listener is not listen on same IP address. Solved problem with moving publication to separate IP and changing internal DNS records.

real problem 1 rule for wpad.dat redirection don't work while any other redirection for web listener work properly.

real problem 2 file named wpad.dat cannot be served from published site for any other purposes.

real problem 1 rule for wpad.dat redirection don't work while any other redirection for web listener work properly.

real problem 2 file named wpad.dat cannot be served from published site for any other purposes.

Any solution?

I had similar problem. One day the wpad.dat was loaded like empty page. Problem was in mistakenly configured web listener, where internal network was also selected in network list. After deselecting internal network and leaving only listening on selected external IPs, wpad.dat started to load correctly.