102 Processing
A WebDAV interim response saying the server accepted the request and is still working on it, so the client should not time out.
What 102 Processing means
102 was defined in RFC 2518 for WebDAV. It let a server tell the client that a long request, such as a COPY or MOVE of a large folder tree, was still in progress.
RFC 4918, which replaced RFC 2518, dropped 102 because few clients supported it. The number is still registered, but you should not rely on it. For long jobs, return 202 Accepted with a status URL instead.
Example response
HTTP/1.1 102 ProcessingHow to check for a 102 response
cURL
# Print only the status code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/JavaScript (Node.js)
const res = await fetch("https://example.com/");
if (res.status === 102) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 102:
print(res.status_code, res.reason)Go
res, err := http.Get("https://example.com/")
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
if res.StatusCode == 102 {
fmt.Println(res.Status)
}Specification
102 Processing is defined in RFC 2518, section 10.1.
Related status codes
- 202
The server accepted the request for processing, but the work has not finished yet and may still fail later.
- 103
An interim response that sends Link headers early so the browser can preload CSS, fonts or scripts while the server builds the page.
- 100
The server got the request headers and has not rejected them, so the client should go ahead and send the request body.