The internal proxy infrastructure has been replaced with a single multiplexed proxy that handles both HTTP and SOCKS4/5 on one port. Previously, separate HTTP and SOCKS proxies listened on separate ports; now a single mux proxy inspects the first byte and routes accordingly.
Details
- On Linux/macOS, the HTTP backend uses a Unix domain socket under
srt-mux-<pid>-<seq>.sock. - On Windows, the HTTP backend falls back to a loopback TCP port.
- The SOCKS handler receives the raw connection directly when the first byte is 0x04 (SOCKS4) or 0x05 (SOCKS5).
- A first-byte timeout destroys idle connections that never send data.
Evidence
New mux proxy (search for "Mux proxy (HTTP+SOCKS) listening on localhost:")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.