-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Uncaught error when using createForHostname() on an expired certificate (due to verify_peer setting) #69
Comments
It's indeed a bug, I'd accept a PR with tests that fixes this. |
Dear contributor, because this issue seems to be inactive for quite some time now, I've automatically closed it. If you feel this issue deserves some attention from my human colleagues feel free to reopen it. |
Can anyone fix this problem please? |
same issue |
I have just started testing this and have encountered the same issue. The method in the original post does work for the time being but this is still a bug it seems. |
same issue here. The workaround seems to solve it |
Hey guys.
I am experiencing this problem when calling
createForHostName()
on a domain, where the certificate is expired.The error appears to be related to the verify_peer setting, as it works when I set it to
false
.Can be reproduced with the following code:
I am able to get the certificate with the following workaround:
Maybe I have just misunderstood something, but shouldn't it be work with
createForHostName()
by default - even though the certificate is expired? :)I'd be happy to submit a pull request, but I'm not too strong in SSL and certificates and figured there might be a reason why you have defaulted to
true
.Here's the full error dump and stack traces:
The text was updated successfully, but these errors were encountered: