**it was not possible to connect to the revocation server or a definitive response could not be obtained**
I am using fiddler classic version:
v5.0.20204.45441 for .NET 4.6.1
We are on a very locked down network, so I am looking for work arounds, not blaming Teleric or Fiddler.
1 Answer, 1 is accepted
Hello,
We can only guess what might be causing the issue on your end, but it appears to be related to a server certificate error. In order to resolve the issue, you can try using the "Ignore server certificate error (unsafe)" option in Fiddler. You can also enable or disable the "Check for certificate revocation" option, which can be accessed through the Tools > Options > HTTPS screen.
Regards,
Nick Iliev
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.
Rank 1
Thanks Nick, Sounded like very good ideas. Yes, it only happens if I have HTTPS decode on.
I tried both together and separately. No luck. Is there any I could do that would help track this down?
Does your company utilize security tools such as F5 or VPN solutions that require downloading the CRL list explicitly? If that is the case, the error prompt you are receiving may be due to a security policy that prevents the certificate list from being accessed while an MITM proxy, such as Fiddler, is in place. In such a case, you should probably contact your system administrators and ask them for a possible solution.
Another thing you could try is our new Fiddler Everywhere. Apart from the system capturing mode (which you tried using with Fiddler Classic) it also has other capturing modes that do not modify the operating system proxy (like independent browser capturing, and terminal capturing). These modes will allow you to test if you can capture traffic without having to modify the system settings or security policies.
Rank 1