Chunked Progress extension to HTTP
draft-lnageleisen-http-chunked-progress-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Loic Nageleisen | ||
Last updated | 2014-10-10 (Latest revision 2014-04-08) | ||
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 describes Chunked Progress, an extension to Transfer-Encoding: Chunked as defined in RFC2616 [RFC2616]. Chunked Progress introduces a backwards-compatible, RFC2616 compliant method to notify the client of transfer advancement in situations where the server has knowledge of progress but cannot know the resource size ahead of time.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)