Is it possible to limit the number of ongoing requests to a server backend defined in reverse_proxy?
My app server sadly does not include this feature, and can become clobbered / overloaded.
The user experience ends up pretty poor: User is forced to wait a long time (20+ seconds as the app server is clobbered), then finally get a 500 error.
Would rather have a hard limit inside caddy itself to either get a 500 right away when the limit is reached and/or redirect the traffic to another server in the reverse_proxy list.
Any insight, help, recommended patterns appreciated!
Yep, sounds right! The fail_duration is needed to enable passive health checks. (I’ll fix the docs, just noticed they’re a bit inconsistent about that.)