HTTP 413 Content Too Large vs 502 Bad Gateway
HTTP 413 (Content Too Large) is a 4xx Client Error response, while 502 (Bad Gateway) is a 5xx Server Error response. 413 indicates that the request payload exceeds the server's size limit. In contrast, 502 means that the server, acting as a gateway or proxy, received an invalid response from the upstream server.
Description
The request payload exceeds the server's size limit.
When You See It
When uploading files that exceed the server's maximum upload size.
How to Fix
Reduce the payload size. Check server limits (Nginx: client_max_body_size, Apache: LimitRequestBody).
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
413 is a 4xx Client Error response, while 502 is a 5xx Server Error response.
HTTP 413: The request payload exceeds the server's size limit.
HTTP 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
You encounter 413 when when uploading files that exceed the server's maximum upload size.
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 413 (Content Too Large): Reduce the payload size. Check server limits (Nginx: client_max_body_size, Apache: LimitRequestBody). For 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.