HTTP 102 Processing — WebDAV Long-Running Request Indicator
About HTTP 102 Processing
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. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: 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. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: 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. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: No action needed — 102 is an informational status indicating work in progress. Wait for the final response code (200, 207, etc.) after the 102 interim responses. If your client does not understand 102, ensure your HTTP library supports interim responses. For WebDAV clients: increase timeout settings to accommodate long operations. Check server logs if 102 is sent repeatedly without a final response — indicates a hung process. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
Is HTTP 102 still used in modern web applications?
It is rarely used outside of WebDAV. Most modern APIs use 202 Accepted for async operations or WebSockets for progress tracking instead.
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