Commit Graph

10 Commits

Author SHA1 Message Date
klzgrad
d20dc7cdee 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.
2021-01-20 19:48:05 +08:00
klzgrad
aa62b9e3ea socket: Add RawConnect method 2021-01-20 19:48:04 +08:00
klzgrad
c91e9ee471 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.
2021-01-20 19:48:04 +08:00
klzgrad
7bc89bbd69 base: Disable trace event 2021-01-20 19:48:03 +08:00
klzgrad
e048b83085 build: Avoid naming conflict in fstatat64 2021-01-20 19:45:07 +08:00
klzgrad
a0874945ae build: Don't fix Y2038 problem with icu 2021-01-20 19:45:06 +08:00
klzgrad
c5c27fd5da build: Remove icu 2021-01-20 19:40:17 +08:00
klzgrad
b9c826961c build: Force determinism in official build 2021-01-20 19:40:17 +08:00
klzgrad
e552a4d36e build: Don't depend on dri in //content/gpu 2021-01-20 19:40:16 +08:00
importer
52d7da878b Import chromium-88.0.4324.96 2021-01-20 19:40:16 +08:00