Feature #2469

OCSP Stapling

Added by holler about 7 years ago. Updated about 1 month ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Missing in 1.5.x:


OCSP stapling was defined in 2006 and allows a web server to retrieve a signed time-stamped message containing the status of its own certificate that is passed to its client. This saves the client the need to make a connection back to the issuing CA to check the status of the certificate. This has both performance and privacy benefits for the client.

This is supported by the following web-servers:

- Apache 2.3 and later
- NginX 1.3.7 and later
- IIS 7.0 and later

Nothing in my favorite Lighttpd yet? :(

Related issues

Related to Feature #2278: OCSP support in lighttpdNew2010-12-10


Updated by stbuehler almost 7 years ago

  • Target version set to 1.4.x


  • No API documentation found: SSL_set_tlsext_status_ocsp_resp == SSL_ctrl(SSL_CTRL_SET_TLSEXT_STATUS_REQ_OCSP_RESP) ?
  • afaics this has to be set in a blocking callback, cache response
    • for files: refresh if needed and file got changed
    • probably won't support retrieving ocsp response over network

Updated by gstrauss almost 4 years ago

  • Category set to TLS

Updated by carpii over 3 years ago

Just adding that I would love to see this in lighty 1.4.x also

[Edit, although 1.4 sounds unlikely. This ticket is a dupe of #2278 ]


Updated by gstrauss over 3 years ago


Updated by gstrauss over 3 years ago

  • Status changed from New to Duplicate

Never say never. :) Adding this to lighttpd 1.4.x is on the table, but not being worked on at the moment.


Updated by gstrauss over 3 years ago

  • Is duplicate of deleted (Feature #2278: OCSP support in lighttpd)

Updated by gstrauss over 3 years ago


Updated by gstrauss over 3 years ago

  • Status changed from Duplicate to Reopened

#2278 requests support for checking CRL/OCSP on certificates received from client.

This ticket requests that lighttpd send OCSP stapling info.


Updated by mxm almost 3 years ago

The Chromium team are pushing Certificate Transparency (CT) hard and have announced that CT will be required from Sep 2017.
OCSP stapling is one of easiest way to implement Signed Certificate Timestamp which is required in CT from the CA to the site operator.
I think now is the best time for the appearance OCSP stapling in Lighty after many years of waitng.


Updated by gstrauss almost 2 years ago

  • Priority changed from Low to Normal

Updated by wschlich about 1 year ago

I'd like to see this feature in lighttpd as well.


Updated by gstrauss about 1 month ago

  • Status changed from Reopened to New

Also available in: Atom