| Previous | Next |
| HTTP_STATUS_SWITCH_PROTOCOLS | HTTP_EARLY_HINTS |
HTTP_STATUS_PROCESSING
HTTP_STATUS_PROCESSING represents HTTP 102 Processing, an informational status originally defined by WebDAV in RFC 2518. It is an interim 1xx response: the server has accepted the complete request and is still processing it, but has not produced the final response. A client must continue waiting for the final status rather than treating 102 as successful completion.
WebDAV history and current protocol handling
RFC 2518 introduced 102 for operations that could take long enough for a client to assume that the connection or request had stalled. RFC 4918 later removed the status from the revised WebDAV specification while explicitly leaving its IANA registration referencing RFC 2518. This historical detail matters when testing old WebDAV clients and servers: support for 102 is not evidence that the final operation succeeded.
For diagnostics, capture the complete response sequence. HTTP permits zero or more informational responses followed by exactly one final response. Check whether a proxy forwards the 102 response, whether the client parser continues reading after it, and which final status terminates the request. A trace containing only 102 is incomplete for determining the outcome.
References
- RFC 2518, 102 Processing — original WebDAV definition.
- RFC 4918, Status Code Extensions to HTTP/1.1 — removal of 102 from the revised specification while retaining its registration reference.
- RFC 9110, Informational 1xx — current processing rules for interim responses.
Looking for a different code? Search another status or error code.