mirror of
https://github.com/klzgrad/naiveproxy.git
synced 2024-11-24 14:26:09 +03:00
4ec614c567
In the socket system, only WebSocket sockets are allowed to tunnel through HTTP/1 proxies. "Raw" sockets in the normal socket pool don't have it, and their CONNECT headers are not sent, instead the raw payload is sent as-is to the HTTP/1 proxy, breaking the proxying. The socket system works like 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. In Naive, we need the normal pool because the WS pool has some extra restrictions but we also need tunneling to produce a client socket with proxy tunneling built in. Therefore force tunneling for all sockets and have them always send CONNECT headers. This will otherwise break regular HTTP client sockets via HTTP/1 proxies, but as we don't use this combination, it is ok. |
||
|---|---|---|
| .. | ||
| base | ||
| build | ||
| build_overrides | ||
| buildtools | ||
| chrome | ||
| components | ||
| crypto | ||
| ios | ||
| ipc | ||
| net | ||
| testing/gtest/include/gtest | ||
| third_party | ||
| tools | ||
| url | ||
| .clang-format | ||
| .gitattributes | ||
| .gn | ||
| AUTHORS | ||
| BUILD.gn | ||
| DEPS | ||
| LICENSE | ||