Hacker News new | ask | show | jobs
by rfd4sgmk8u 1494 days ago
I discount this approach. It is necessary but not sufficient to pass on simple browser SSL tests. There are other complexities that are best left to the browser to negotiate the session.
1 comments

What are the things that you think are best handled by the browser while negotiating a session?
The connection parameters including encryption parameters and certificate from the origin. There are a lot of weird rules in WebPKI you may miss, this is beyond a general purpose TLS library.

Enforcing Certificate Transparency rules or CAA records, is the proxy doing this?

Which browser enforces CAA?

it's a certificate misissuance, but AFAIK it's not up to the browser.