HTTP 102 Processing vs 502 Bad Gateway
HTTP 102 (Processing) is a 1xx Informational response, while 502 (Bad Gateway) 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, 502 means that the server, acting as a gateway or proxy, received an invalid response from the upstream server.
설명
The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
이 코드를 보게 되는 경우
During long-running WebDAV operations.
해결 방법
Wait for the final response. This is an interim status to prevent timeouts.
설명
The server, acting as a gateway or proxy, received an invalid response from the upstream server.
이 코드를 보게 되는 경우
When Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
해결 방법
Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.
주요 차이점
102 is a 1xx Informational response, while 502 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 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
You encounter 102 when during long-running WebDAV operations.
You encounter 502 when when Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
언제 어떤 것을 사용할지
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.