1# Proxy Auto Config Using WPAD 2 3Most systems support manually configuring a proxy for web access, but this is 4cumbersome and kind of techical, so Chrome also supports 5[WPAD](http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol) for proxy 6configuration (enabled if "automatically detect proxy settings" is enabled on 7Windows). 8 9## Problem 10 11Currently, WPAD is pretty slow when we're starting up Chrome - we have to query 12the local network for WPAD servers using DNS (and maybe NetBIOS), and we wait 13all the way until the resolver timeout before we try sending any HTTP requests 14if there's no WPAD server. This is a really crappy user experience, since the 15browser's basically unusable for a couple of seconds after startup if 16autoconfig is turned on and there's no WPAD server. 17 18## Solution 19 20There's a couple of simplifying assumptions we make: 21 22* If there is a WPAD server, it is on the same network as us, and hence likely 23 to respond to lookups far more quickly than a random internet DNS server 24 would. 25* If we get a lookup success for WPAD, there's overwhelmingly likely to be a 26 live WPAD server. The WPAD script could also be large (!?) whereas the DNS 27 response is necessarily small. 28 29Therefore our proposed solution is that when we're trying to do WPAD resolution, 30we fail very fast if the WPAD server doesn't immediately respond to a lookup 31(like, 100ms or less). If there's no WPAD server, we'll time the lookup out in 32100ms and get ourselves out of the critical path much faster. We won't time out 33lookups for explicitly-configured WPAD servers (i.e., custom PAC script URLs) in 34this fashion; those will still use the normal DNS timeout. 35 36**This could have bad effects on networks with slow DNS or WPAD servers**, so we 37should be careful to allow users to turn this off, and we should keep statistics 38as to how often lookups succeed after the timeout. 39 40So here's what our WPAD lookup policy looks like **currently** in practice 41(assuming WPAD is enabled throughout): 42 43* If there's no WPAD server on the network, we try to do a lookup for WPAD, 44 time out after two seconds, and disable WPAD. Until this time, no requests 45 can proceed. 46* If there's a WPAD server and our lookup for it answers in under two seconds, 47 we use that WPAD server (fetch and execute its script) and proceed with 48 requests. 49* If there's a WPAD server and our lookup for it answers after two seconds, we 50 time out and do not use it (ever) until a network change triggers a WPAD 51 reconfiguration. 52 53Here's what the **proposed** lookup policy looks like in practice: 54 55* If there's no WPAD server on the network, we try to do a lookup for WPAD, 56 time out after 100ms, and disable WPAD. 57* If there's a WPAD server and our lookup for it answers in under 100ms or 58 it's explicitly configured (via a custom PAC URL), we use that WPAD server. 59* If there's a WPAD server and our lookup for it answers after 100ms, we time 60 out and do not use it until a network change. 61