rather a regular http proxy that every browser supports
And exactly as expected, they have a MSFT stack so they're wedged and think changing the spec is the right way to solve it. Sigh.
> With TLS 1.2 we can ask the end user to take a Wireshark trace and then decrypt it with the RSA private key. With TLS 1.3 we will have to rely on the SSLKEYLOGFILE feature in Firefox and Chrome, so we want it to be available. Unfortunately, Microsoft does not allow this functionality, which is a problem in a TLS 1.3 only environment.
