Abhinav Singh

Thanks, @briantting for reporting this and https://github.com/abhinavsingh/proxy.py/issues/45 . I am wondering what exactly is your use case that runs into these issues. Can you expand a little on that?

Thanks, @briantting, good to hear that. I observed issues you reported are encountered when packets are sent to `proxy.py` in a specific way, most likely if `proxy.py` is used in...

@briantting Is it possible for you to give it another shot and/or provide raw requests being sent to `proxy.py`. Thank you.

@briantting If possible can you attach a sample raw request you tried sending to `proxy.py`. Thank you.

With https://github.com/abhinavsingh/proxy.py/issues/75 merged into develop branch, I believe this should work out now. Please try again and verify. Thank you.

I did run into a similar issue during development. **This seems to be a MacOS specific issue, that too when proxy.py is set up as a system-wide MacOS HTTP/HTTPS proxy.**...

Thank you @NariyoshiChida , looks like the email landed in my spam box because it was not encrypted :(. Apologies for the same. One good thing is that, vulnerability is...

Let's turn this into an `enhancement`, as its a known issue and `ConnectionPool` is a WIP, as advertised by its flag description `Default: False. (WIP) Enable upstream connection pooling`. Other...

@JerryKwan Assigned it back to you, it mades more sense as you are working on it.

@JerryKwan This update is unrelated to your PR. Something that I ran into and I wanted to document here for posterity: `ConnectionPool` is now `UpstreamConnectionPool`. Today, I tried it with...