HTTP 101 Switching Protocols vs 502 Bad Gateway
HTTP 101 (Switching Protocols) is a 1xx Informational response, while 502 (Bad Gateway) is a 5xx Server Error response. 101 indicates that the server understands the Upgrade header field request and indicates which protocol it is switching to. In contrast, 502 means that the server, acting as a gateway or proxy, received an invalid response from the upstream server.
Beschreibung
The server understands the Upgrade header field request and indicates which protocol it is switching to.
Wann Sie es sehen
When upgrading from HTTP/1.1 to WebSocket, or to HTTP/2.
Wie man es behebt
This is normal behavior during protocol upgrades. Ensure your client supports the target protocol.
Beschreibung
The server, acting as a gateway or proxy, received an invalid response from the upstream server.
Wann Sie es sehen
When Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
Wie man es behebt
Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.
Wesentliche Unterschiede
101 is a 1xx Informational response, while 502 is a 5xx Server Error response.
HTTP 101: The server understands the Upgrade header field request and indicates which protocol it is switching to.
HTTP 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
You encounter 101 when when upgrading from HTTP/1.1 to WebSocket, or to HTTP/2.
You encounter 502 when when Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
Wann welchen verwenden
For 101 (Switching Protocols): This is normal behavior during protocol upgrades. Ensure your client supports the target protocol. For 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.