Reverse HTTP Transport
draft-bt-httpbis-reverse-http-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Benjamin M. Schwartz , Tirumaleswar Reddy.K , Mohamed Boucadair , Philipp S. Tiesel | ||
| Last updated | 2024-04-25 (Latest revision 2023-10-23) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 a secure transport for HTTP in which the client and server roles are reversed. This arrangement improves the origin server's protection from Layer 3 and Layer 4 denial-of-service attacks when an intermediary is in use. It allows origin server's to be hosted without being publicly (and directly) accessible but allows clients to access these servers via an intermediary.
Authors
Benjamin M. Schwartz
Tirumaleswar Reddy.K
Mohamed Boucadair
Philipp S. Tiesel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)