HTTP 104 — Upload Resumption Supported
HTTP 104
Upload Resumption Supported
A provisional code signalling that the server supports resumable uploads.
What 104 actually means
This is a temporary registration attached to an unfinished IETF draft on resumable uploads, not a finished standard. The idea is that a server can answer the start of an upload with a 104 plus a location the client can use to resume from if the connection drops. Treat it as experimental: the number and the semantics can still change before the draft becomes an RFC.
Common causes
- A client and server are negotiating the draft resumable-uploads protocol
- An upload service implementing the IETF draft ahead of standardisation
If you're just trying to view the page
- Nothing — this is protocol negotiation and never surfaces as a page
- If an upload tool reports it as an error, the tool is mishandling an interim response; check for an update
If it's your site
- Do not depend on 104 in production; the draft is not final and the code is a provisional registration
- Use the well-established alternatives — tus, or S3 multipart uploads — for resumable uploads you need to ship today
Reference
- Status code
- 104
- Reason phrase
- Upload Resumption Supported
- Category
- 1xx — Informational
- Defined in
- draft-ietf-httpbis-resumable-upload (temporary registration)
Common questions
- What does HTTP 104 mean?
- A provisional code signalling that the server supports resumable uploads. This is a temporary registration attached to an unfinished IETF draft on resumable uploads, not a finished standard. The idea is that a server can answer the start of an upload with a 104 plus a location the client can use to resume from if the connection drops.
- How do I fix a 104 error?
- Nothing — this is protocol negotiation and never surfaces as a page
- Is 104 a client error or a server error?
- 104 is in the 1xx range, which means informational. It is not an error at all.
Related pages
- 101 Switching Protocols The connection is being upgraded from HTTP to another protocol, usually WebSocke
- 103 Early Hints The server sends resource hints early so the browser can start downloading asset
- 100 Continue The server has read your request headers and wants you to send the body.
- 102 Processing A WebDAV server is still working on a long request and is telling the client not