HTTP registry: destination_not_found
The intermediary cannot determine the appropriate next hop to use for this request; for example, it may not be configured. Note that this error is specific to gateways, which typically require specific configuration to identify the "backend" server; forward proxies use in-band information to identify the origin server.
Proxy and gateway values describe processing across trust boundaries where fields, authority, and framing may be transformed. destination_not_found is registered in HTTP Proxy Error Types. Defining reference: rfc9209.
Identifier (http)
destination_not_found
The intermediary cannot determine the appropriate next hop to use for this request; for example, it may not be configured. Note that this error is specific to gateways, which typically require specific configuration to identify the "backend" server; forward proxies use in-band information to identify the origin server.
Strip hop-by-hop data, normalize framing, trust forwarded metadata only from configured proxies, and avoid exposing topology or credentials.
This registry value is currently marked active by IANA. Follow the defining specification before sending, accepting, or proxying it.
IANA registry: http-proxy-status/http-proxy-error-types
Registry reference: rfc9209
Sources