Commit Graph

9 Commits

Author SHA1 Message Date
klzgrad
6be19f063d 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.
2019-12-14 17:07:34 +08:00
klzgrad
55e481a4ee socket: Add RawConnect method 2019-12-14 17:07:32 +08:00
klzgrad
2b6c41901a 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.
2019-12-14 16:30:52 +08:00
klzgrad
9b053f4622 build: Disable use_pangocario 2019-12-14 16:30:52 +08:00
klzgrad
94362a0660 build: Remove icu 2019-12-14 16:30:52 +08:00
klzgrad
bd64e325e4 build: Force determinism in official build 2019-12-14 16:30:52 +08:00
klzgrad
c983975d02 build: Move exclude_unwind_tables back into declare_args
There is desire to adjust this flag manually.

BUG=762629
R=thakis@chromium.org

Change-Id: I3bd134c19270cd1f729b3ea078674e734493d4ab
2019-12-14 16:30:52 +08:00
klzgrad
dd6f8c8192 build: Don't depend on dri in //content/gpu 2019-12-14 16:30:51 +08:00
klzgrad
09ab1f292c Import chromium-79.0.3945.79 2019-12-14 16:30:51 +08:00