Ok, now it works here too and I didn't change a thing. Very strange. Yesterday
I tried it dozens of times (even side by side with my Windows 10 machine where
it always worked) and it never worked. So the problem is solved now but still
it's not exactly relieving to see this error just vanish... somewhat inside me
tells me that it can probably come back at any time :/

On 05.01.2019 at 11:48 Andreas Falkenhahn via curl-library wrote:

> Any idea where to look for that in Windows? But once again, if it were
> generelly impossible for Windows to contact the revocation servers it'd
> be pretty certain that it was a configuration/firewall/whatever issue.
> But the strange thing is that Windows can't contact the revocation servers
> *only* for specific domains, i.e. the *.de one works, but for the *.com one
> it can't contact the revocation server. But it's not as if *.com didn't
> work at all, e.g. https://www.paypal.com/ works fine, but for my *.com
> domain it doesn't work at all.

> BTW, I don't have any antivirus software on said Windows 7 machine and
> I also tried disabling the firewall altogether - all to no avail :/

> On 05.01.2019 at 00:50 Ray Satiro via curl-library wrote:

>> Works here as well. I suggest figure out why Windows can't
>> contact the revocation servers. It's not curl that makes those
>> connections. If you really have to disable revocation checking
>> recent versions have --ssl-no-revoke [1] and CURLSSLOPT_NO_REVOKE

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-01-05