Package: tinyproxy Version: 1.11.1-2 Severity: normal Dear Maintainer,
While evaluating tinyproxy upstream proxy cascading behavior when routed through rotating 4G/5G mobile gateways (network topology test setup documented at https://pxm2.io/guides/ ), tinyproxy drops persistent HTTP/1.1 client connections when the upstream mobile carrier reassigns the CGNAT bearer IP. Under standard HTTP/1.1 persistent connection rules defined in IETF RFC 7230 Section 6.3 ( https://datatracker.ietf.org/doc/html/rfc7230 ), intermediary proxy gateways should handle upstream socket termination gracefully rather than closing active client sockets abruptly without a 502 or 504 status response. Upstream commits in the Tinyproxy repository ( https://github.com/tinyproxy/tinyproxy ) show socket read/write timeouts in src/reqs.c during proxy handshake. Steps to reproduce: 1. Configure tinyproxy with upstream proxy pointing to a mobile carrier gateway. 2. Force IP change on the upstream mobile bearer. 3. Attempt subsequent HTTP CONNECT requests over the existing keepalive connection. 4. Observed: connection terminated with reset by peer rather than handled recovery. Best regards, Sebastiano Pignato
