HTTP 102 Processing vs 200 OK
HTTP 102 (Processing) is a 1xx Informational response, while 200 (OK) is a 2xx Success response. 102 indicates that the server has received and is processing the request, but no response is available yet. Prevents the client from timing out. In contrast, 200 means that the request succeeded. The meaning depends on the HTTP method: GET returns the resource, POST reports the action result, HEAD returns headers only.
Description
The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
When You See It
During long-running WebDAV operations.
How to Fix
Wait for the final response. This is an interim status to prevent timeouts.
Description
The request succeeded. The meaning depends on the HTTP method: GET returns the resource, POST reports the action result, HEAD returns headers only.
When You See It
The most common HTTP response — indicates the request was processed successfully.
How to Fix
No fix needed. The request succeeded as expected.
Key Differences
102 is a 1xx Informational response, while 200 is a 2xx Success response.
HTTP 102: The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
HTTP 200: The request succeeded. The meaning depends on the HTTP method: GET returns the resource, POST reports the action result, HEAD returns headers only.
You encounter 102 when during long-running WebDAV operations.
You encounter 200 when the most common HTTP response — indicates the request was processed successfully.
When to Use Which
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 200 (OK): No fix needed. The request succeeded as expected.