HTTP 102 Processing — Meaning, Causes & How to Fix
The server has received and is processing the request, but no response is available yet (WebDAV).
- Code
- 102
- Name
- Processing
- Class
- 1xx Informational
- Specification
- RFC 2518 (WebDAV)
- Cacheable by default
- Not applicable (interim response)
What HTTP 102 means
102 Processing is an interim response from the original WebDAV specification. It told the client that a long-running request (for example a recursive COPY or MOVE) was still being worked on, so the client would not time out. It was left out of the later WebDAV revision (RFC 4918) and is rarely used today.
Common causes
- A WebDAV server handling a slow, multi-resource operation.
How to fix it
For site owners
- For long jobs in a modern API, prefer returning 202 Accepted with a status URL the client can poll.
For visitors & developers
- Treat it as informational and keep waiting for the final response.
SEO impact
No SEO impact. It is never a final response.
Example 102 response
HTTP/1.1 102 Processing
HTTP/1.1 207 Multi-Status
Content-Type: application/xml; charset=utf-8Related status codes
Check or look up another code
Search and filter every code in the HTTP Status Codes tool, browse the full list by class, or read HTTP status codes explained: the complete developer guide.
Open HTTP Status Codes tool →All status codesFrequently asked questions
What does HTTP 102 mean?
HTTP 102 Processing is a 1xx Informational status code. The server has received and is processing the request, but no response is available yet (WebDAV).
Is 102 Processing still in use?
Rarely. It was dropped from RFC 4918, the current WebDAV spec. For long-running work, 202 Accepted plus a polling or callback URL is the usual pattern.
Which specification defines 102?
It is defined in RFC 2518 (WebDAV).
Is a 102 response cacheable?
No. 102 is an interim (1xx) response; only the final response that follows can be cached.