-
Notifications
You must be signed in to change notification settings - Fork 51
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
unable to connect to https://localhost #21
Comments
Hmm, I don't think there's much Can you link to the other tools you use and how they allow you to disable certificate checking? |
I only mean things like wget which has a --no-check-certificate flag. I
think what you've said sounds correct, that it depends on what options
there are in whatever is managing the HTTP request. That it's localhost has
no significance, particularly, that's just a common example of a site that
wouldn't - couldn't - have a valid certificate.
…On Fri, Sep 7, 2018 at 5:14 PM Filip Hracek ***@***.***> wrote:
Hmm, I don't think there's much linkcheck can do here. From its own
perspective, it's merely connecting to a server (it doesn't know it's a
localhost one). I'll have to investigate if there's a way to switch off
certificate checking on some low level API.
Can you link to the other tools you use and how they allow you to disable
certificate checking?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABLWyh9rt8i9m-3Yh69ofufPJITt4XYHks5uYwvIgaJpZM4Wd3iB>
.
|
+1 for a solution to this if you can think of one. It should be possible to turn off cert checking, or specify a particular cert as trusted. (Otherwise, linkcheck is fantastic, and I thank you for your great work.) |
The only message is "connection failed". It's a self-signed certificate, for other similar utilities I have to turn off certificate checking in some fashion. I can crawl the live public version of the same site, which has a valid cert, so I'd guess that's some part of the problem.
The text was updated successfully, but these errors were encountered: