All RPC interfaces for a given node (see rpc_interfaces) currently support HTTP/1.1. A specific RPC interface can also support HTTP/2 by setting the "app_protocol" configuration entry to "HTTP2" for that interface.


Support for HTTP/2 is currently experimental (e.g. only a single stream per session is supported). See for progress updates.


Operators can cap the size of client HTTP requests (body and header) for each RPC interface in the http_configuration configuration section. These configuration entries are optional and have sensible default values.

If a client HTTP request breaches any of these values, the client is returned a 413 or 431 HTTP error and the session is automatically closed by the CCF node.