HTTP 502 Bad Gateway indicates that a server acting as a gateway or proxy received an invalid response from an upstream server. This is NOT a problem with the client or the gateway itself — the upstream server returned something the gateway couldn't understand. Common causes: upstream server crashed mid-response, SSL certificate mismatch between gateway and upstream, upstream returned malformed HTTP, or upstream closed the connection unexpectedly.
Response includes the status code, standard headers (including Content-Type), and a small diagnostic JSON body describing the request and returned status.
Simulator URL (copy in the app after load — not a normal link):
https://httpstatus.com/api/status/502
Example request:
curl -i "https://httpstatus.com/api/status/502"