New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no-verify not the same as curl --insecure #315
Comments
The option you need is This is a nasty gotcha in the way we interpret options. Maybe we should print a warning/suggestion if a TLS error happens and you passed |
Something like this could also be helpful if we add cURL's Would it be enough to print a warning as soon we detect a negation flag has no effect and is too similar to another flag? |
when connecting to a self signed cert with an unknown issuer, passing
--no-verify
still throws this error:When I run the same command with curl
--insecure
, it works.I don't have a great understanding of SSL, so appreciate any insight here.
The text was updated successfully, but these errors were encountered: