You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pass certificate name mismatch through to client.
The intent was that when the server's certificate doesn't match the
domain name the client expects, we would generate a certificate that
gives the client the same name-mismatch error. But when we decided to
generate certificates with only a single hostname instead of the full
list provided by the server, we broke that behavior, thus masking
certificate name mismatches. This commit restores the correct behavior.
Don't assume clients will catch everything but an UnknownAuthorityError.
If a certificate's name doesn't match the site's hostname, or it's
expired, we can assume that clients will catch the problem even if we
give them a certificate that's signed by a CA they trust. But we were
including several other types of errors in that treatment as well,
most notably NoValidChains (which is the one returned for the eMudhra
intermediate certificates).
Use net/http instead of x/net/http2
Functionality is being moved from x/net/http2 to net/http, with the
eventual goal of deprecating x/net/http2. So we're following along.
Refine platform detection from headers
Check the Sec-CH-UA-Platform hint, which Chrome always includes.
As of this commit, ~20% of requests contain this header.
For a slight optimization, exit early when no header value is found.