HTTP 205 Reset Content vs 502 Bad Gateway
HTTP 205 (Reset Content) is a 2xx Success response, while 502 (Bad Gateway) is a 5xx Server Error response. 205 indicates that the server fulfilled the request and the client should reset the document view (e.g., clear a form). In contrast, 502 means that the server, acting as a gateway or proxy, received an invalid response from the upstream server.
Description
The server fulfilled the request and the client should reset the document view (e.g., clear a form).
When You See It
After form submissions where the server wants the client to reset the form for new input.
How to Fix
The client should clear the form or reset the view. Rarely used in practice.
Description
The server, acting as a gateway or proxy, received an invalid response from the upstream server.
When You See It
When Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
How to Fix
Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.
Key Differences
205 is a 2xx Success response, while 502 is a 5xx Server Error response.
HTTP 205: The server fulfilled the request and the client should reset the document view (e.g., clear a form).
HTTP 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
You encounter 205 when after form submissions where the server wants the client to reset the form for new input.
You encounter 502 when when Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
When to Use Which
For 205 (Reset Content): The client should clear the form or reset the view. Rarely used in practice. For 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.