Question: OCSP stapling decreases the load on a PKI infrastructure's OCSP server by attaching a signed OCSP response to the target in a TLS connection. In addition it creates a more secure/private session since the CA doesn't know that your browser is accessing a given site. Some people have compared this behavior to Kerberos.

**Question**

* What web browsers support OCSP stapling?
* Are there any implementation considerations among different browsers that need to be addressed to maintain uniform privacy and performance benefits?

Answer: 
My impression is that [OCSP stapling is not well supported on the client side](https://web.archive.org/web/20151017004901/https://blogs.msdn.com/b/ieinternals/archive/2011/04/07/10151106.aspx?Redirected=true), but it's possible my information might be out of date.

Firefox apparently supports OCSP stapling, as of Firefox 26. (Thanks to Jan Schejbal for this information.)

Chrome supports OCSP stapling [on Windows, Linux, and ChromeOS](https://web.archive.org/web/20151216040743/https://code.google.com/p/chromium/issues/detail?id=361230#c8). (Thanks to Kit Sunde for this information.) (The Chrome team has [decided](https://arstechnica.com/information-technology/2012/02/google-strips-chrome-of-ssl-revocation-checking/) that they plan to [remove CRL and regular OCSP checks](https://www.imperialviolet.org/2012/02/05/crlsets.html), but they haven't disabled OCSP stapling.)

I've read one report that [most browsers support OCSP stapling on Windows](https://news.netcraft.com/archives/2013/07/19/microsoft-achieves-world-domination-in-ocsp-stapling.html).

Here is some more information on [browser support for OCSP](https://web.archive.org/web/20220307083919/http://www.carbonwind.net/blog/post/Random-SSLTLS-101-OCSPCRL-in-practice.aspx) (but not OCSP stapling, unfortunately).
IE has supported it since Vista, Chrome supports it on Windows via CryptoAPI and on other platforms via patches to NSS it made that Firefox has not accepted, Opera has also supported it for several years. Firefox has the worst revocation behavior of any browser on a number of fronts its lack of support of OCSP stapling being the smallest example. Also Chrome will continue to support OCSP and OCSP stapling in enterprise scenarios they have provided their own revocation checking mechanism for a variety of reasons.