Processing
An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.
What it means
The HTTP 102 Processing status code is a WebDAV extension. It indicates that the server has received and is processing the request, but no response is available yet.
It is used to prevent the client from timing out while waiting for a response to a complex request that takes significant time to process (e.g., a WebDAV 'PROPFIND' request over a large directory tree).
How it works
- 1The client sends a complex request that takes a long time.
- 2The server realizes processing will take longer than standard client timeouts.
- 3The server sends a '102 Processing' interim response to reset the client's timeout timer.
- 4The server eventually sends the final response (e.g., 200 OK or 207 Multi-Status).
Why you're seeing this
- • The server is taking too long to process a WebDAV request.
How to fix it
- • If you are building a standard REST API and are considering using 102 Processing because your endpoints are slow, consider refactoring to an asynchronous job queue model (return 202 Accepted with a polling URL) instead.
Framework Implementations
Express.js
app.post('/heavy-task', (req, res) => {
// Send interim response (not natively supported by Express res.status without closing)
res.write('HTTP/1.1 102 Processing\r\n\r\n');
// ... do heavy work ...
res.end('Final response');
});Real-Life Scenarios
It is rarely used outside of WebDAV. For modern APIs, Server-Sent Events, WebSockets, or asynchronous job queues (HTTP 202 Accepted) are generally preferred over 102 Processing.
WebDAV Directory Operations
A client requests a deep copy of a massive directory structure using WebDAV. The server sends 102 to keep the connection alive while it copies files.
HTTP Transaction
1. Client Request
PROPFIND /large-directory HTTP/1.1 Host: webdav.example.com Depth: infinity
2. Server Response
HTTP/1.1 102 Processing (Minutes later...) HTTP/1.1 207 Multi-Status Content-Type: application/xml <?xml version="1.0"...>
SEO Implications
Googlebot and other search engines do not generally encounter or process WebDAV operations, so 102 Processing has no SEO impact.