Variant
send-error-detail
Information about errors encountered by sent requests.
variant send-error-detail {
dns-timeout,
dns-error(dns-error-detail),
destination-not-found,
destination-unavailable,
destination-ip-unroutable,
connection-refused,
connection-terminated,
connection-timeout,
connection-limit-reached,
tls-certificate-error,
tls-configuration-error,
http-incomplete-response,
http-response-header-section-too-large,
http-response-body-too-large,
http-response-timeout,
http-response-status-invalid,
http-upgrade-failed,
http-protocol-error,
http-request-cache-key-invalid,
http-request-uri-invalid,
internal-error,
tls-alert-received(tls-alert-received-detail),
tls-protocol-error,
h2-error(h2-error-detail),
extra(extra-send-error-detail),
}Cases
| Case | Payload | Description |
|---|---|---|
| dns-timeout | — | The system encountered a timeout when trying to find an IP address for the backend hostname. |
| dns-error | dns-error-detail | The system encountered a DNS error when trying to find an IP address for the backend hostname. |
| destination-not-found | — | The system cannot determine which backend to use, or the specified backend was invalid. |
| destination-unavailable | — | The system considers the backend to be unavailable, for example when recent attempts to communicate with it may have failed, or a health check may indicate that it is down. |
| destination-ip-unroutable | — | The system cannot find a route to the next-hop IP address. |
| connection-refused | — | The system's connection to the backend was refused. |
| connection-terminated | — | The system's connection to the backend was closed before a complete response was received. |
| connection-timeout | — | The system's attempt to open a connection to the backend timed out. |
| connection-limit-reached | — | The system is configured to limit the number of connections it has to the backend, and that limit has been exceeded. |
| tls-certificate-error | — | The system encountered an error when verifying the certificate presented by the backend. |
| tls-configuration-error | — | The system encountered an error with the backend TLS configuration. |
| http-incomplete-response | — | The system received an incomplete response to the request from the backend. |
| http-response-header-section-too-large | — | The system received a response to the request whose header section was considered too large. |
| http-response-body-too-large | — | The system received a response to the request whose body was considered too large. |
| http-response-timeout | — | The system reached a configured time limit waiting for the complete response. |
| http-response-status-invalid | — | The system received a response to the request whose status code or reason phrase was invalid. |
| http-upgrade-failed | — | The process of negotiating an upgrade of the HTTP version between the system and the backend failed. |
| http-protocol-error | — | The system encountered an HTTP protocol error when communicating with the backend. |
| http-request-cache-key-invalid | — | An invalid cache key was provided for the request. |
| http-request-uri-invalid | — | An invalid URI was provided for the request. |
| internal-error | — | The system encountered an unexpected internal error. |
| tls-alert-received | tls-alert-received-detail | The system received a TLS alert from the backend. |
| tls-protocol-error | — | The system encountered a TLS error when communicating with the backend, either during the handshake or afterwards. |
| h2-error | h2-error-detail | The system received an HTTP/2 error frame and code from the backend. |
| extra | extra-send-error-detail | Additional error details may be added in the future via this resource type. |