Abhinav Singh

@cat-policlot Thank you for the update. Looks like even though `threaded` mode was enabled, internal core is trying to use `recv_handle` for socket sharing. This results into error because it's...

@cat-policlot WINERROR 10022 indicates an invalid argument was supplied. This could happen for a variety of reasons, sometimes outside of `proxy.py` control. E.g. this can happen if underlying socket was...

@cat-policlot jFYI, `IS_WINDOWS` detection was fixed in #1196. Can you give it a try when you get a chance. Also were you able to figure out `WINERROR` problem. Was it...

@cat-policlot Closing this since `IS_WINDOWS` detection was fixed in #1196. However, I haven't had a chance to try it out yet. Someone with access to Cygwin must verify the fix....

@sam-kleiner Thanks for bringing this to my notice. Indeed currently hostname check is hardcoded here https://github.com/abhinavsingh/proxy.py/blob/06a84ae6b004325f35b8eb108e0e186078fb0e07/proxy/core/connection/server.py#L42 In future release I will look to expose these via existing (or new) proxy...

@sam-kleiner Another quick option which came to me while updating title of this issue: 1. We can add a boolean command line flag which indicates whether to bypass cert check...

> --upstream-verify localhost=/path/to/cert --upstream-verify nginx.local=/path/to/cert2 This is an even better option :). Looking to address this for upcoming `v2.4.0` release.

> hi, do we have a boolean command line flag which indicates whether to bypass cert check for self-signed upstreams now? thanks for your reply. @abhinavsingh Hi Lyz, Unfortunately no....

@thiagobenine @lyz04551 Thank you for bringing this back. It got off the radar somehow. Lemme jump onto this over the coming weekend. Hopefully we'll have something out soon. Best

Thank you @nettnikl for bringing this to attention. I'll try add some clarity by updating docs and examples. Best