caddy icon indicating copy to clipboard operation
caddy copied to clipboard

`/reverse_proxy/upstreams` - all in-flight requests

Open matburton opened this issue 7 months ago • 0 comments

Issue Details

This is a feature request

The Caddy API exposes a useful /reverse_proxy/upstreams end-point which lists the number of in-flight requests for each upstream address, e.g.:

[
  {
    "address": "something:80",
    "num_requests": 1337,
    "fails": 0
  }
]

When the config changes however, and the upstream address for a reverse_proxy is changed, the previous address is no longer included in the JSON returned by /reverse_proxy/upstreams even if there are outstanding requests that have yet to complete.

It'd be awesome if /reverse_proxy/upstreams could include all in-flight requests even if they are to addresses that are no longer an address in the config.

Doing so would allow the /reverse_proxy/upstreams end-point to be useful to determine when a previous upstream has been completely drained.

Assistance Disclosure

AI not used

If AI was used, describe the extent to which it was used.

No response

matburton avatar Sep 26 '25 12:09 matburton