Radiator Server Documentation — v10.34.1

http

The HTTP backend enables Radiator to make HTTP requests to external web services for authentication and authorization purposes.

Health Monitoring

HTTP backends have no SLO by default. Add a service-level-objective block to enable automatic circuit breaking and exponential backoff.

When an explicit service-level-objective block is present, omitted fields use the standard defaults (failure-rate 3/5, initial-backoff-period 3s, max-backoff-period 30s, recovery-probe-count 2). See Service Level Objective for details.

Only infrastructure-level HTTP responses count as failures toward the SLO:

  • 5xx — server-side errors (the backend is crashing or misconfigured)
  • 429 Too Many Requests — the backend is overloaded or rate-limiting

Application-level responses such as 401 Unauthorized, 403 Forbidden, and 404 Not Found are valid AAA outcomes and do not affect the failure rate.

Request retries

Generic HTTP backends do not retry by default. Use the retry block to configure additional attempts, their delay, and the timeout, request error, or HTTP status conditions that warrant a retry.