ProxymanApp / ProxymanApp/Proxyman

Toggling Block List Drops Non-matching Active Connections

Open
#714 7 comments 0 reactions 1 assignee View on GitHub

@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
  1. 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

  1. Establish a connection to the server in another terminal via Proxyman:

curl -x "http://localhost:9090" http://localhost:9191

  1. Confirm the connection shows up in Proxyman as "ACTIVE".

  2. In Proxyman, add and enable a Block List rule that does not match. For example:

ANY http://example/

  1. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.