RFC 9440: Client-Cert HTTP Header Field

This document describes HTTP extension header fields that allow a TLS terminating reverse proxy (TTRP) to convey the client certificate information of a…

Read RFC 9440 on the RFC Editor

Outgoing relationships (16 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Normative reference — RFC 9110: HTTP Semantics
Normative reference — RFC 8941: Structured Field Values for HTTP
Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Informative reference — RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3
Informative reference — RFC 9113: HTTP/2
Informative reference — RFC 9114: HTTP/3
Informative reference — RFC 9112: HTTP/1.1
Informative reference — RFC 7468: Textual Encodings of PKIX, PKCS, and CMS Structures
Informative reference — RFC 7239: Forwarded HTTP Extension
Informative reference — RFC 6585: Additional HTTP Status Codes
Informative reference — RFC 7541: HPACK: Header Compression for HTTP/2
Informative reference — RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
Informative reference — RFC 9204: QPACK: Field Compression for HTTP/3

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 9421: HTTP Message Signatures
Informatively referenced by — RFC 9635: Grant Negotiation and Authorization Protocol (GNAP)
Informatively referenced by — RFC 9700: Best Current Practice for OAuth 2.0 Security