Problem:
In Caddy v1, the forward_proxy plugin supported response_timeout, but this was dropped in v2. Because timeouts are currently handled globally at the server level, it is impossible to set different response timeouts for different proxy endpoints or Unix sockets running within the same Caddy instance.
Proposed Solution:
Reintroduce a timeout configuration option inside the forward_proxy directive to allow granular, per-block timeout control.
Alternatives Considered:
Running separate Caddy instances with different global configurations adds massive operational overhead and complexity, making it an unviable workaround for multi-socket setups.
Problem:
In Caddy v1, the forward_proxy plugin supported response_timeout, but this was dropped in v2. Because timeouts are currently handled globally at the server level, it is impossible to set different response timeouts for different proxy endpoints or Unix sockets running within the same Caddy instance.
Proposed Solution:
Reintroduce a timeout configuration option inside the forward_proxy directive to allow granular, per-block timeout control.
Alternatives Considered:
Running separate Caddy instances with different global configurations adds massive operational overhead and complexity, making it an unviable workaround for multi-socket setups.