Commit Graph

5 Commits

Author SHA1 Message Date
klzgrad
3d3f835d9c socket: Force tunneling for all sockets
After the upstream large refactor, now only WebSocket sockets
have tunneling via HTTP/1 proxies. "Raw" sockets in the normal
socket pool don't have tunneling via HTTP/1 proxies, i.e.
CONNECT headers are not sent, instead the raw payload is sent
as-is to the HTTP/1 proxy, which makes it not work.

For the reference the official code does this:

- HTTP sockets via HTTP/1 proxies: normal pool, no tunneling.
- HTTPS sockets via HTTP/1 proxies: normal pool, no tunneling
  but does its own proxy encapsulation.
- WS sockets via HTTP/1 proxies: WS pool, tunneling.

We want the normal pool because the WS pool has some extra
restrictions but we also want tunneling to expose a client socket
with the proxy built in.

Therefore we can force tunneling for all sockets. This will always
send CONNECT headers first and thus break HTTP client sockets via
HTTP/1 proxies, but since we don't use this combination this is ok.
2020-02-05 22:06:50 +08:00
klzgrad
326f644453 socket: Add RawConnect method 2020-02-05 22:06:50 +08:00
klzgrad
90e99d35bf socket: Allow higher limits for proxies
As an intermediary proxy we should not enforce stricter connection
limits in addition to what the user is already enforcing.
2020-02-05 22:06:50 +08:00
klzgrad
bb5eb399f2 build: Remove icu 2020-02-05 22:06:50 +08:00
klzgrad
83cda03016 Import chromium-80.0.3987.87 2020-02-05 22:06:49 +08:00