Template-Driven HTTP CONNECT Proxying for TCP
draft-schwartz-httpbis-connect-tcp-01
| Document | Type |
Replaced Internet-Draft
(httpbis WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Benjamin M. Schwartz | ||
| Last updated | 2023-05-17 (Latest revision 2023-03-09) | ||
| Replaced by | draft-ietf-httpbis-connect-tcp | ||
| 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-connect-tcp | |
| 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
TCP proxying using HTTP CONNECT has long been part of the core HTTP specification. However, this proxying functionality has several important deficiencies in modern HTTP environments. This specification defines an alternative HTTP proxy service configuration for TCP connections. This configuration is described by a URI Template, similar to the CONNECT-UDP and CONNECT-IP protocols.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)