[GH-ISSUE #1717] The connection still be ACTIVE even client side has abort the connection #1710

New issue

Open

opened 2026-03-03 19:53:42 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 19:53:42 +03:00

Owner

Originally created by @Liu-huaicheng on GitHub (Jul 15, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1717

Description

Steps to Reproduce

Make a route path which won't response instantly, like:

app.get('/timeout', (req, res) => {
    setTimeout(() => {
    res.send('Hello World!')
    }, 140000);
});

Request that path via curl and abort it

 curl -v http://localhost:3000/timeout

Current Behavior

The connection still be Active on proxyman after the connection has been aborted on terminal

Expected Behavior

The connection should be aborted on proxyman immediately after it is aborted on client side

Environment

App version: Proxyman Version 4.8.2 (48020)
macOS version: Version 13.4 (22F66)

Originally created by @Liu-huaicheng on GitHub (Jul 15, 2023). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1717 ## Description ![image](https://github.com/ProxymanApp/Proxyman/assets/57707288/9a511eaa-0d06-4862-a7d1-c18e91a24820) ## Steps to Reproduce  1. Make a route path which won't response instantly, like: ``` app.get('/timeout', (req, res) => { setTimeout(() => { res.send('Hello World!') }, 140000); }); ``` 2. Request that path via `curl` and abort it ``` curl -v http://localhost:3000/timeout ``` ## Current Behavior The connection still be **Active** on proxyman after the connection has been aborted on terminal ## Expected Behavior The connection should be aborted on proxyman immediately after it is aborted on client side ## Environment - App version: Proxyman Version 4.8.2 (48020) - macOS version: Version 13.4 (22F66)