HTTP 201 Created vs 502 Bad Gateway
HTTP 201 (Created) is a 2xx Success response, while 502 (Bad Gateway) is a 5xx Server Error response. 201 indicates that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity. In contrast, 502 means that the server, acting as a gateway or proxy, received an invalid response from the upstream server.
Description
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
When You See It
After successfully creating a new user, post, order, or other resource via a REST API.
How to Fix
No fix needed. Check the Location header for the URL of the new resource.
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
201 is a 2xx Success response, while 502 is a 5xx Server Error response.
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
HTTP 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
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 201 (Created): No fix needed. Check the Location header for the URL of the new resource. For 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.