{"version":"2.1.196","anchor":"mux-proxy-combined-http-socks-proxy","canonical_anchor":"mux-proxy-combined-http-socks-proxy","heading":"Mux Proxy (Combined HTTP+SOCKS Proxy)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196\/e\/mux-proxy-combined-http-socks-proxy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196","markdown":"### Mux Proxy (Combined HTTP+SOCKS Proxy)\n\nThe 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.\n\n**Details**\n\n- On Linux\/macOS, the HTTP backend uses a Unix domain socket under `srt-mux-<pid>-<seq>.sock`.\n- On Windows, the HTTP backend falls back to a loopback TCP port.\n- The SOCKS handler receives the raw connection directly when the first byte is 0x04 (SOCKS4) or 0x05 (SOCKS5).\n- A first-byte timeout destroys idle connections that never send data.\n\n**Evidence**\n\nNew mux proxy (search for `\"Mux proxy (HTTP+SOCKS) listening on localhost:\"`)"}