Brad Fitzpatrick 10f48087f4 net/tshttpproxy: call winhttp calls from a fixed OS thread ...

We often see things in logs like:

2021-03-02 17:52:45.2456258 +0800 +0800: winhttp: Open: The parameter is incorrect.
2021-03-02 17:52:45.2506261 +0800 +0800: tshttpproxy: winhttp: GetProxyForURL("https://log.tailscale.io/c/tailnode.log.tailscale.io/5037bb42f4bc330e2d6143e191a7ff7e837c6be538139231de69a439536e0d68"): ERROR_INVALID_PARAMETER [unexpected]

I have a hunch that WinHTTP has thread-local state. If so, this would fix it.
If not, this is pretty harmless.

Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

2021-03-03 19:16:04 -08:00

..

tshttpproxy_future.go

tshttp, derphttp: send Proxy-Authorization, not Authorization, to proxies

2020-08-28 21:01:00 -07:00

tshttpproxy_test.go

net/tshttpproxy: support HTTP proxy environment credentials on Windows too

2021-02-18 08:27:37 -08:00

tshttpproxy_windows.go

net/tshttpproxy: call winhttp calls from a fixed OS thread

2021-03-03 19:16:04 -08:00

tshttpproxy.go

net/tshttpproxy: support HTTP proxy environment credentials on Windows too

2021-02-18 08:27:37 -08:00