Timeline for Secure connection failed (OCSP)
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 26, 2014 at 17:28 | comment | added | Tom Leek | @user3371321: Firefox supports OCSP stapling. This means that if the server decides to send an OCSP response along with its certificate, Firefox will be able to process it. However, it does not make stapling usage mandatory. Moreover, "major websites" must also support other browsers which do not support stapling, so not-stapled OCSP ought to work as well. | |
| May 13, 2014 at 13:54 | comment | added | JimiDini | Wikipedia doesn't use OCSP Stapling: ssllabs.com/ssltest/… Neither does google: ssllabs.com/ssltest/… | |
| May 13, 2014 at 13:05 | comment | added | user3371321 | Firefox uses OCSP stapling, so it it is (or should be) Google and Wikipedia contacting the OCSP server and not me. Firefox will only contact the OCSP server directly if Google/Wikipedia send me an invalid stapled response or no stapled response at all; and I fail to understand why two major websites would do that. See blog.mozilla.org/security/2013/07/29/ocsp-stapling-in-firefox. | |
| May 4, 2014 at 10:53 | history | answered | JimiDini | CC BY-SA 3.0 |