More
More
102 Processing
A WebDAV server has accepted the request and is still working on it, so the client should not time out yet.
- Code
102- Reason phrase
- Processing
- Class
- 1xx Informational
- Defined in
- RFC 2518 section 10.1
- Status
- Deprecated: RFC 4918 removed it from WebDAV, though the registry still lists it.
- Cacheable by default
- No
What it means
An interim response: the server sends it before the final one, and the client keeps waiting.
Common causes. Long WebDAV operations such as copying a large folder.
What to do. Nothing. The code is deprecated and few servers send it now.
How clients and crawlers treat it
Google Search. An interim response has no effect on indexing; Google acts on the final status that follows it. Source: Google Search Central, How HTTP status codes, and network and DNS errors affect Google Search.
Caching. Never cached: an interim response is not a final answer to the request.
Example response
HTTP/1.1 102 Processing (the final response follows on the same connection)
Applications almost never send a 1xx response by hand: the web server or HTTP library produces it as part of the protocol.
Related codes
- 101Switching ProtocolsThe server agrees to change protocol on this connection, as the client asked in its Upgrade header.
- 103Early HintsThe server sends some headers, usually Link preload hints, before the final response is ready.
- 100ContinueThe server has received the request headers and the client can go ahead and send the body.
All status codes · All 1xx codes
Names and numbers from the IANA HTTP Status Code Registry. Google Search behaviour as documented by Google Search Central.