Resumable Uploads for HTTP
draft-ietf-httpbis-resumable-upload-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Marius Kleidl , Guoye Zhang , Lucas Pardue | ||
| Last updated | 2023-09-03 (Latest revision 2023-03-02) | ||
| Replaces | draft-tus-httpbis-resumable-uploads-protocol | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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
HTTP clients often encounter interrupted data transfers as a result of canceled requests or dropped connections. Prior to interruption, part of a representation may have been exchanged. To complete the data transfer of the entire representation, it is often desirable to issue subsequent requests that transfer only the remainder of the representation. HTTP range requests support this concept of resumable downloads from server to client. This document describes a mechanism that supports resumable uploads from client to server using HTTP.
Authors
Marius Kleidl
Guoye Zhang
Lucas Pardue
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)