ProxymanApp / ProxymanApp/Proxyman
Toggling Block List Drops Non-matching Active Connections
@NghiaTranUIT is already working on this.
Since Dec 2, 2020.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Proxyman version? (Ex. Proxyman 1.4.3)
Version 2.14.1 (21410)
macOS Version? (Ex. mac 10.14)
10.14.6 (18G6042)
Steps to reproduce
- Stand up a server that can support long connections. To reproduce, we can just use netcat and never respond. In one terminal, run:
nc -l 9191
- Establish a connection to the server in another terminal via Proxyman:
curl -x "http://localhost:9090" http://localhost:9191
-
Confirm the connection shows up in Proxyman as "ACTIVE".
-
In Proxyman, add and enable a Block List rule that does not match. For example:
ANY http://example/
- The connection is killed and the client errors:
curl: (52) Empty reply from server
Expected behavior
Since http://localhost:9191 does not match the blocklist rule ANY http://example/, I would not expect that connection to be dropped. I am trying to block connections to a particular server, but it is dropping active connections to other non-matching servers too.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.