klzgrad 281b43ba2a net/socket: Force tunneling for all sockets ...

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.

2025-03-07 20:53:22 +08:00

src

net/socket: Force tunneling for all sockets

2025-03-07 20:53:22 +08:00

.gitignore

Add .gitignore

2025-03-05 21:09:18 +08:00

Description

Make a fortune quietly

BSD-3-Clause 639 MiB

Languages

C++ 80.5%

Python 15.1%

C 1.3%

Objective-C++ 1.1%

Starlark 0.5%

Other 1.3%