Bad gateway

What to do next

• Retry only when it is safe for the operation. Contact support if the issue persists.

HTTP response contract

Set the actual HTTP status to 502 and Content-Type: application/problem+json. The JSON status below must agree with the actual response status.

RFC-defined members

type

The canonical URI above; clients use it as the primary problem identifier.

title

Bad gateway — a stable human-readable summary (localization is permitted).

status

502 — advisory in the body; it does not set the HTTP status.

detail

A safe explanation specific to this occurrence. Clients should not parse it for machine decisions.

instance

An optional URI reference identifying a specific occurrence. It need not resolve; avoid sensitive identifiers.

These five members are defined by RFC 9457. This template includes type, title, status, and detail in its samples; RFC 9457 does not require all five.

Custom extension fields

This definition declares no custom extensions.

Extensions belong to this type’s contract. Consumers must ignore extensions they do not recognize.

Example response body

Illustrative occurrence data. Construct the response manually in your application or automation.

{
  "type": "https://errors.ctrlbox.dev/problems/bad-gateway",
  "title": "Bad gateway",
  "status": 502,
  "detail": "A server acting as a gateway or proxy received an invalid response from an upstream server."
}