HTTP 102 Processing vs 303 See Other
HTTP 102 (Processing) is a 1xx Informational response, while 303 (See Other) is a 3xx Redirection 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, 303 means that the server is redirecting to a different resource using GET, typically after a POST operation (Post/Redirect/Get pattern).
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 server is redirecting to a different resource using GET, typically after a POST operation (Post/Redirect/Get pattern).
When You See It
After form submissions to prevent resubmission on browser refresh.
How to Fix
Follow the Location header with a GET request. This is intentional — part of the PRG pattern.
Key Differences
102 is a 1xx Informational response, while 303 is a 3xx Redirection 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 303: The server is redirecting to a different resource using GET, typically after a POST operation (Post/Redirect/Get pattern).
You encounter 102 when during long-running WebDAV operations.
You encounter 303 when after form submissions to prevent resubmission on browser refresh.
When to Use Which
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 303 (See Other): Follow the Location header with a GET request. This is intentional — part of the PRG pattern.