Maximilian Hils

The downside of both raw OpenSSL knobs and a high-level `Connection.set_host` method is that both APIs are unsafe by default. Not all developers will be aware that `set_host` almost always...

Also FWIW, [here](https://github.com/mitmproxy/mitmproxy/blob/244ff35e606e8ae7ca8aa15d7529566a97ec69f5/mitmproxy/addons/tlsconfig.py#L288-L307) is the hostname logic we have in mitmproxy - it's pretty similar to the CPython one, but uses cryptography bindings instead.

A combination of `from __future__ import annotations` and the `type` statement should indeed do the trick. It's probably possible to extend this here: https://github.com/mitmproxy/pdoc/blob/891605516a25c0f66dc184ce60754e76dbbe239e/pdoc/_compat.py#L25-L29 to support typing-extensions (try import for

This is mostly blocked by the lack of (hosted) arm64 runners on GitHub. If I understand things correctly they are getting into beta this month. :)

Maybe more importantly: We already provide arm64 docker images you can use. That'd be my current recommendation for Raspberry Pis and such. :)

What do you mean by "see ignored request"? Are you looking for the entire HTTP request line, or just the hostname?

@nneonneo: if an option would make your life easier, I'd be more than happy to merge a PR for now without asking any further questions. Very grateful for your help...

You can compile the JS with `npm start prod`: https://github.com/mitmproxy/mitmproxy/blob/main/release/release.py#L79-L83 :)

Which specific additional options would you want to add, and which additional use cases do they enable? > It would also be nice one day to reintroduce the multi-peer support...

Escape key works, but I agree that a button would be good.