The HTTP Wrap Up Capsule
draft-schinazi-httpbis-wrap-up-01
| Document | Type |
Replaced Internet-Draft
(httpbis WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | David Schinazi , Lucas Pardue | ||
| Last updated | 2025-01-08 (Latest revision 2024-10-16) | ||
| Replaced by | draft-ietf-httpbis-wrap-up | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-wrap-up | |
| Consensus boilerplate | Yes | ||
| 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
HTTP intermediaries sometimes need to terminate long-lived request streams in order to facilitate load balancing or impose data limits. However, Web browsers commonly cannot retry failed proxied requests when they cannot ascertain whether an in-progress request was acted on. To avoid user-visible failures, it is best for the intermediary to inform the client of upcoming request stream terminations in advance of the actual termination so that the client can wrap up existing operations related to that stream and start sending new work to a different stream or connection. This document specifies a new "WRAP_UP" capsule that allows a proxy to instruct a client that it should not start new requests on a tunneled connection, while still allowing it to finish existing requests.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)