7 Commits

Author SHA1 Message Date
klzgrad
d65c0560aa 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-05-20 21:46:12 +08:00
klzgrad
167dfdd4ed socket: Add RawConnect method 2020-05-20 21:46:11 +08:00
klzgrad
679e2a7115 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-05-20 21:46:11 +08:00
klzgrad
380da5583a build: Remove icu 2020-05-20 21:46:11 +08:00
klzgrad
cde72524fa build: Force determinism in official build 2020-05-20 21:46:11 +08:00
klzgrad
fc1df222ee build: Don't depend on dri in //content/gpu 2020-05-20 20:33:55 +08:00
klzgrad
21e78728f8 Import chromium-83.0.4103.61 2020-05-20 20:33:54 +08:00