Client-Cert HTTP Header: Conveying Client Certificate Information from TLS Terminating Reverse Proxies to Origin Server Applications
draft-bdc-something-something-certificate-05
| Document | Type |
Replaced Internet-Draft
(httpbis WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Brian Campbell | ||
| Last updated | 2021-05-09 (Latest revision 2021-03-23) | ||
| Replaced by | draft-ietf-httpbis-client-cert-field | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-client-cert-field | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines the HTTP header field "Client-Cert" that allows a TLS terminating reverse proxy to convey the client certificate of a mutually-authenticated TLS connection to the origin server in a common and predictable manner.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)