fb392e34b5
There was a mechanism in tshttpproxy to note that a Windows proxy lookup failed and to stop hitting it so often. But that turns out to fire a lot (no PAC file configured at all results in a proxy lookup), so after the first proxy lookup, we were enabling the "omg something's wrong, stop looking up proxies" bit for awhile, which was then also preventing the normal Go environment-based proxy lookups from working. This at least fixes environment-based proxies. Plenty of other Windows-specific proxy work remains (using WinHttpGetIEProxyConfigForCurrentUser instead of just PAC files, ignoring certain types of errors, etc), but this should fix the regression reported in #4811. Updates #4811 Change-Id: I665e1891897d58e290163bda5ca51a22a017c5f9 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com> |
||
|---|---|---|
| .. | ||
| mksyscall.go | ||
| tshttpproxy.go | ||
| tshttpproxy_future.go | ||
| tshttpproxy_linux.go | ||
| tshttpproxy_synology.go | ||
| tshttpproxy_synology_test.go | ||
| tshttpproxy_test.go | ||
| tshttpproxy_windows.go | ||
| zsyscall_windows.go | ||