Closed mikpe closed 8 months ago
It is not clear to me what the default was before OTP-26. Was it verify_none
? In other words: will this change keep the behavior as it was before release 26, or will it change it?
The default prior to OTP-26 was verify_none
, so this change preserves existing behaviour.
The
ssl
changes in OTP-26 mean that any code that doesn't specifyverify_none
will default toverify_peer
, and unless certs are passed in you get hard errors. This also affectshttpc:request
. Update uses of the latter to explicitly pass inverify_none
.