{verify, verify_peer} warning or error
Olivier Boudeville
olivier.boudeville@REDACTED
Fri Sep 10 20:04:59 CEST 2021
Hi,
And on a related subject, I was wondering why the warning being
discussed in this thread was not suppressed when using:
httpc:request(get,
{"https://acme-staging-v02.api.letsencrypt.org/directory", []},
[{ssl, [{verify, *verify_none*}]}], []).
=WARNING REPORT==== 10-Sep-2021::19:54:29.258613 ===
Description: "Authenticity is not established by certificate path
validation"
Reason: "Option {verify, verify_peer} and cacertfile/cacerts is
missing"
{ok,{{"HTTP/1.1",200,"OK"},
[{"cache-control","public, max-age=0, no-cache"},
[...]
(OTP 24.0 ; once initialised with inets:start() and ssl:start() )
Thanks in advance for any hint,
Best regards,
Olivier.
--
Olivier Boudeville
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20210910/5d891e30/attachment.htm>
More information about the erlang-questions
mailing list