HTTP 104 Unassigned

HTTP 104 is an unassigned status code with no official definition in the IANA HTTP status code registry or any published RFC. IANA lists it as unassigned. If you encounter a 104 response, it is generated by a non-standard or proprietary application using an undocumented code.

HTTP 104 full guide โ†’

Quick reference

Code104
NameUnassigned
Category1xx Informational
SpecificationIANA Registry (Unassigned)
IANA statusUnassigned โ€” no official definition
CacheableNo
Client actionTreat as an unrecognized 1xx response and ignore it per RFC 9110.
In-depth guideHTTP 104 full guide โ†’

What HTTP 104 means

IANA's HTTP status code registry lists 104 as unassigned โ€” it has not been claimed by any RFC or specification. Despite this, some applications return 104 for proprietary or non-standard purposes. Without context from the specific application returning it, 104 has no defined meaning.

RFC 9110 specifies that HTTP status codes are extensible, and 1xx codes in particular are informational interim responses. Per RFC 9110, a client that receives an unrecognized 1xx status code must ignore it โ€” 1xx responses are not final and do not represent the outcome of the request. The final response will follow.

If you encounter 104 in server logs or API responses, check the documentation for the system generating it, as it is a proprietary extension code with no standard definition.

Assigned 1xx codes

CodeNameStatus
100ContinueAssigned
101Switching ProtocolsAssigned
102ProcessingAssigned (WebDAV)
103Early HintsAssigned
104-199UnassignedNot defined

FAQ

What does HTTP 104 mean?

HTTP 104 has no official definition โ€” IANA lists it as unassigned. If you see it, it is from a system using a non-standard code. Check that system's documentation for the specific meaning.

How should a client handle an unrecognized 1xx code?

RFC 9110 says clients must ignore unrecognized 1xx responses. They are informational and interim โ€” the final response will still arrive on the same connection.

Could 104 be assigned in the future?

Yes. Unassigned codes can be claimed by future RFCs. If a future RFC assigns 104 to a specific meaning, the IANA registry will be updated and that assignment will become the standard definition.

Related resources

On this site: HTTP 104 โ€” full guide ยท HTTP 100 Continue ยท HTTP 101 Switching Protocols ยท HTTP 103 Early Hints

Standards: IANA HTTP Status Code Registry