HTTP 102 Processing vs 401 Unauthorized
HTTP 102 (Processing) is a 1xx Informational response, while 401 (Unauthorized) is a 4xx Client Error 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, 401 means that the request requires user authentication. The response includes a WWW-Authenticate header indicating the authentication scheme.
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 requires user authentication. The response includes a WWW-Authenticate header indicating the authentication scheme.
When You See It
When accessing a protected resource without credentials or with expired tokens.
How to Fix
Include valid authentication credentials (API key, Bearer token, Basic auth) in the Authorization header.
Key Differences
102 is a 1xx Informational response, while 401 is a 4xx Client Error 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 401: The request requires user authentication. The response includes a WWW-Authenticate header indicating the authentication scheme.
You encounter 102 when during long-running WebDAV operations.
You encounter 401 when when accessing a protected resource without credentials or with expired tokens.
When to Use Which
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 401 (Unauthorized): Include valid authentication credentials (API key, Bearer token, Basic auth) in the Authorization header.