{verify, verify_peer} warning or error
Bram Verburg
bram.verburg@REDACTED
Fri Sep 10 16:26:28 CEST 2021
This should help you get going making HTTPS requests using httpc:
https://erlef.github.io/security-wg/secure_coding_and_deployment_hardening/ssl
On Fri, Sep 10, 2021 at 17:17, pablo platt <pablo.platt@REDACTED> wrote:
> Hi,
>
> When I'm sending a request to content.googleapis.com without the verify ssl option I'm getting a warning:
> Url = "https://content.googleapis.com/youtube/v3/videos",
> httpc:request(get,
> {Url, []},
> [],
> []).
>
> Description: "Authenticity is not established by certificate path validation"
> Reason: "Option {verify, verify_peer} and cacertfile/cacerts is missing"
>
> When I'm adding the verify_peer option I'm getting an error:
> Url = "https://content.googleapis.com/youtube/v3/videos",
> httpc:request(get,
> {Url, []},
> [{ssl, [{verify, verify_peer}]}],
> []).
>
> {error,{failed_connect,[{to_address,{"content.googleapis.com",
> 443}},
> {inet,[inet],{options,{cacertfile,[]}}}]}}
>
> What is the correct way to send the request?
>
> Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20210910/bc82fb2e/attachment.htm>
More information about the erlang-questions
mailing list