---
name: "libressl-SSL_CTX_set_tlsext_status_cb"
section: "3"
platform: "linux"
package: "libressl"
version: "4.4.0-1"
release: "Arch Linux 2026-11-01"
platforms: ["linux"]
url: "https://new.carta.tech/libressl-SSL_CTX_set_tlsext_status_cb"
---

# libressl-SSL\_CTX\_set\_tlsext\_status\_cb(3)

OCSP Certificate Status Request functions

## NAME

**SSL\_CTX\_set\_tlsext\_status\_cb**, **SSL\_CTX\_get\_tlsext\_status\_cb**, **SSL\_CTX\_set\_tlsext\_status\_arg**, **SSL\_CTX\_get\_tlsext\_status\_arg**, **SSL\_set\_tlsext\_status\_type**, **SSL\_get\_tlsext\_status\_type**, **SSL\_get\_tlsext\_status\_ocsp\_resp**, **SSL\_set\_tlsext\_status\_ocsp\_resp** – OCSP Certificate Status Request functions

## SYNOPSIS

SSL Library (libssl, -lssl) libcrypto

**#include \<openssl/tls1.h\>**

*long*\

**SSL\_CTX\_set\_tlsext\_status\_cb**(*SSL\_CTX \*ctx*, *int (\*callback)(SSL \*, void \*)*);

*long*\

**SSL\_CTX\_get\_tlsext\_status\_cb**(*SSL\_CTX \*ctx*, *int (\*callback)(SSL \*, void \*)*);

*long*\

**SSL\_CTX\_set\_tlsext\_status\_arg**(*SSL\_CTX \*ctx*, *void \*arg*);

*long*\

**SSL\_CTX\_get\_tlsext\_status\_arg**(*SSL\_CTX \*ctx*, *void \*\*arg*);

*long*\

**SSL\_set\_tlsext\_status\_type**(*SSL \*s*, *int type*);

*long*\

**SSL\_get\_tlsext\_status\_type**(*SSL \*s*);

*long*\

**SSL\_get\_tlsext\_status\_ocsp\_resp**(*ssl*, *unsigned char \*\*resp*);

*long*\

**SSL\_set\_tlsext\_status\_ocsp\_resp**(*ssl*, *unsigned char \*resp*, *int len*);

## DESCRIPTION

A client application may request that a server send back an OCSP status response (also known as OCSP stapling). To do so the client should call the **SSL\_set\_tlsext\_status\_type**() function on an individual *SSL* object prior to the start of the handshake. Currently the only supported type is TLSEXT\_STATUSTYPE\_ocsp. This value should be passed in the *type* argument.

The client should additionally provide a callback function to decide what to do with the returned OCSP response by calling **SSL\_CTX\_set\_tlsext\_status\_cb**(). The callback function should determine whether the returned OCSP response is acceptable or not. The callback will be passed as an argument the value previously set via a call to **SSL\_CTX\_set\_tlsext\_status\_arg**(). Note that the callback will not be called in the event of a handshake where session resumption occurs (because there are no Certificates exchanged in such a handshake).

The callback previously set via **SSL\_CTX\_set\_tlsext\_status\_cb**() can be retrieved by calling **SSL\_CTX\_get\_tlsext\_status\_cb**(), and the argument by calling **SSL\_CTX\_get\_tlsext\_status\_arg**().

On the client side, **SSL\_get\_tlsext\_status\_type**() can be used to determine whether the client has previously called **SSL\_set\_tlsext\_status\_type**(). It will return TLSEXT\_STATUSTYPE\_ocsp if it has been called or -1 otherwise. On the server side, **SSL\_get\_tlsext\_status\_type**() can be used to determine whether the client requested OCSP stapling. If the client requested it, then this function will return TLSEXT\_STATUSTYPE\_ocsp, or -1 otherwise.

The response returned by the server can be obtained via a call to **SSL\_get\_tlsext\_status\_ocsp\_resp**(). The value \**resp* will be updated to point to the OCSP response data and the return value will be the length of that data. If the server has not provided any response data, then \**resp* will be NULL and the return value from **SSL\_get\_tlsext\_status\_ocsp\_resp**() will be -1.

A server application must also call the **SSL\_CTX\_set\_tlsext\_status\_cb**() function if it wants to be able to provide clients with OCSP Certificate Status responses. Typically the server callback would obtain the server certificate that is being sent back to the client via a call to SSL\_get\_certificate(3), obtain the OCSP response to be sent back, and then set that response data by calling **SSL\_set\_tlsext\_status\_ocsp\_resp**(). A pointer to the response data should be provided in the *resp* argument, and the length of that data should be in the *len* argument.

## RETURN VALUES

The callback when used on the client side should return a negative value on error, 0 if the response is not acceptable (in which case the handshake will fail), or a positive value if it is acceptable.

The callback when used on the server side should return with either SSL\_TLSEXT\_ERR\_OK (meaning that the OCSP response that has been set should be returned), SSL\_TLSEXT\_ERR\_NOACK (meaning that an OCSP response should not be returned), or SSL\_TLSEXT\_ERR\_ALERT\_FATAL (meaning that a fatal error has occurred).

**SSL\_CTX\_set\_tlsext\_status\_cb**(), **SSL\_CTX\_get\_tlsext\_status\_cb**(), **SSL\_CTX\_set\_tlsext\_status\_arg**(), **SSL\_CTX\_get\_tlsext\_status\_arg**(), **SSL\_set\_tlsext\_status\_type**(), and **SSL\_set\_tlsext\_status\_ocsp\_resp**() always return 1, indicating success.

**SSL\_get\_tlsext\_status\_type**() returns TLSEXT\_STATUSTYPE\_ocsp on the client side if **SSL\_set\_tlsext\_status\_type**() was previously called, or on the server side if the client requested OCSP stapling. Otherwise -1 is returned.

**SSL\_get\_tlsext\_status\_ocsp\_resp**() returns the length of the OCSP response data or -1 if there is no OCSP response data.

## SEE ALSO

[ssl(3)](/ssl/3.md), SSL\_CTX\_callback\_ctrl(3)

## HISTORY

**SSL\_CTX\_set\_tlsext\_status\_cb**(), **SSL\_CTX\_set\_tlsext\_status\_arg**(), **SSL\_set\_tlsext\_status\_type**(), **SSL\_get\_tlsext\_status\_ocsp\_resp**(), and **SSL\_set\_tlsext\_status\_ocsp\_resp**() first appeared in OpenSSL 0.9.8h and have been available since OpenBSD 4.5.

**SSL\_CTX\_get\_tlsext\_status\_cb**() and **SSL\_CTX\_get\_tlsext\_status\_arg**() first appeared in OpenSSL 1.1.0 and have been available since OpenBSD 6.3.

**SSL\_get\_tlsext\_status\_type**() first appeared in OpenSSL 1.1.0 and has been available since OpenBSD 7.0.