jesse
jesse copied to clipboard
pass verify_none to httpc:request
The ssl changes in OTP-26 mean that any code that doesn't specify verify_none will default to verify_peer, and unless certs are passed in you get hard errors. This also affects httpc:request. Update uses of the latter to explicitly pass in verify_none.
I wonder how hard would it be to make it configurable (eg, via application env)?
Probably not very, but I haven't looked since my goal was to preserve existing (pre OTP-26) behaviour.
Ping - can someone merge this?