102 Processing (WebDAV; RFC 2518)

This is an educational reference page about HTTP 102 Processing. The page itself is served as 200 OK so it can be indexed as HTTP documentation.

A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.

What it means

HTTP 102 Processing means the server has received a WebDAV request and is still processing it, but does not have a final response yet.

Common causes

A WebDAV request contains many file operations or sub-requests.
The server needs more time but wants to keep the client connection alive.
The client might otherwise assume the request timed out.

How to fix it

Use 102 only as an interim response before the final status code.
Send a final 2xx, 4xx, or 5xx response when processing completes.
Use timeouts, progress reporting, or async jobs when operations can take a long time.

Example response

HTTP/1.1 102 Processing

HTTP/1.1 207 Multi-Status
Content-Type: application/xml

Developer notes

102 is mainly associated with WebDAV. It is not a final success response.

Questions

What does HTTP 102 mean?

HTTP 102 means the server is still processing the request and has not sent the final response yet.

Is 102 Processing a final response?

No. 102 Processing is an interim response. The server still needs to send a final HTTP response.

When is HTTP 102 used?

HTTP 102 is used when a long-running WebDAV request is being processed and the server wants to prevent client timeout assumptions.