HTTP 102 Processing vs 500 Internal Server Error
HTTP 102 (Processing) is a 1xx Informational response, while 500 (Internal Server Error) is a 5xx Server 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, 500 means that the server encountered an unexpected condition that prevented it from fulfilling the request. A generic catch-all for server-side errors.
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 encountered an unexpected condition that prevented it from fulfilling the request. A generic catch-all for server-side errors.
When You See It
When an unhandled exception occurs, a database connection fails, or server code has a bug.
How to Fix
Check server logs for the stack trace. Common causes: unhandled exceptions, database errors, misconfigurations.
Key Differences
102 is a 1xx Informational response, while 500 is a 5xx Server 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 500: The server encountered an unexpected condition that prevented it from fulfilling the request. A generic catch-all for server-side errors.
You encounter 102 when during long-running WebDAV operations.
You encounter 500 when when an unhandled exception occurs, a database connection fails, or server code has a bug.
When to Use Which
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 500 (Internal Server Error): Check server logs for the stack trace. Common causes: unhandled exceptions, database errors, misconfigurations.