What is the difference between 102 Processing and 202 Accepted?

102 is an interim response — the server will still send a final response. 202 is a final response indicating the request was accepted but processing is not complete.

Can browsers handle HTTP 102?

Most browsers ignore 102 responses as they are not commonly used in standard web browsing. They wait for the final response.

HTTP 102 Processing — WebDAV Long-Running Request Indicator

Informational1xx informational

Overview

Understand HTTP 102 Processing status code used in WebDAV to indicate the server has received the request but has not yet completed it, preventing client timeouts.

Key Details

HTTP 102 Processing is a WebDAV extension status code defined in RFC 2518
Sent as an interim response to prevent the client from timing out during long operations
Commonly seen during large file operations like COPY, MOVE, or PROPFIND on collections
The server sends 102 periodically until the final response is ready
Not part of standard HTTP/1.1 — only relevant for WebDAV-enabled servers

Common Causes

Server performing a lengthy WebDAV operation such as recursive COPY
Large PROPFIND requests scanning deep directory hierarchies
Server-side processing taking longer than typical HTTP timeout thresholds
Batch operations on multiple resources within a single WebDAV request

Steps

1No action needed — 102 is an informational status indicating work in progress
2Wait for the final response code (200, 207, etc.) after the 102 interim responses
3If your client does not understand 102, ensure your HTTP library supports interim responses
4For WebDAV clients: increase timeout settings to accommodate long operations
5Check server logs if 102 is sent repeatedly without a final response — indicates a hung process