Aymeric Augustin
Aymeric Augustin
Well, going from this PoC to a properly tested implementation that supports all cases (HTTP/HTTPS => HTTP/HTTPS) is rather boring. I haven't been motivated to do it. Besides writing tests:...
Python 3.7 added [start_tls](https://docs.python.org/3/library/asyncio-eventloop.html?highlight=start_tls#asyncio.loop.start_tls), which removes the need for the ugly hack. If we use it, proxying to a WSS endpoint will require Python ≥ 3.7. I think that's fine.
Thanks for the PR. The approach looks correct. Currently websockets has no external dependencies. I'll take a look at how hard it is to reproduce the digest auth algorithm. Probably...
Are you making connections with `connect` or receiving connections with `serve`?
OK. This isn't currently implemented.
This feature request is for implemting: https://tools.ietf.org/html/rfc7231#section-4.3.6 We must take care of handling TLS properly: - connect with or without TLS to the proxy - connect with or without TLS...
I have a patch that manages the four cases: TLS / not TLS between client and proxy / proxy and server. The patch needs tests and I'm not sure how...
TLS between proxy and server is very messy due to https://bugs.python.org/issue23749 Also we're likely to run into issues like https://github.com/aio-libs/aiosmtpd/issues/83 until we add code to handle that.
I can consider that bug resolved after I drop support for all Python versions before 3.7, about five years from now.