HTTP 207 Multi-Status vs 502 Bad Gateway
HTTP 207 (Multi-Status) is a 2xx Success response, while 502 (Bad Gateway) is a 5xx Server Error response. 207 indicates that the response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV). In contrast, 502 means that the server, acting as a gateway or proxy, received an invalid response from the upstream server.
Description
The response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV).
When You See It
In WebDAV operations that affect multiple resources simultaneously.
How to Fix
Parse the XML body to check the status of each individual 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
207 is a 2xx Success response, while 502 is a 5xx Server Error response.
HTTP 207: The response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV).
HTTP 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
You encounter 207 when in WebDAV operations that affect multiple resources simultaneously.
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 207 (Multi-Status): Parse the XML body to check the status of each individual resource. For 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.