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
This issue is copy & pasted from haskell/wreq#84 and example modified for http-client-tls.
badssl.com tests have wildcard certificate with common name *.badssl.com and Subject Alternative Names badssl.com and *.badssl.com. http-client-tls misinterpretes how wildcard certificates should be handled:
Matching is performed using the matching rules specified by [RFC2459]. If more than one identity of a given type is present in the certificate (e.g., more than one dNSName name, a match in any one of the set is considered acceptable.) Names may contain the wildcard character * which is considered to match any single domain name component or component fragment. E.g., .a.com matches foo.a.com but not bar.foo.a.com. f.com matches foo.com but not bar.com.
Chrome, Firefox and Safari don't allow connection to this test host.
This issue is copy & pasted from haskell/wreq#84 and example modified for
http-client-tls
.badssl.com tests have wildcard certificate with common name
*.badssl.com
and Subject Alternative Namesbadssl.com
and*.badssl.com
.http-client-tls
misinterpretes how wildcard certificates should be handled:RFC2818 states that:
Chrome, Firefox and Safari don't allow connection to this test host.
This was found with TryTLS test tool: https://github.com/ouspg/trytls
The text was updated successfully, but these errors were encountered: