On Fri, Jan 8, 2016 at 10:18 AM, Jim Jagielski <[email protected]> wrote: > I am thinking about the actual health-check impl a bit more, > hence the lack of commits. As noted, initially I was thinking > about optional functions, defined in mod_proxy_http, mod_proxy_ajp, > etc. Then I started thinking that maybe doing it via providers > might be better, allowing for more "custom" health checks via > the end user. Then I started thinking about doing it rough-and- > ready and just adding 'em in mod_proxy_hcheck... > > Before I spend too much time on this, any prefs one way or > another regarding this?
I haven't looked at the architecture so far -- but I think basics in mod_proxy_hcheck and at least one "standalone" provider (as an example) would be a good middle ground. Maybe the standalone one would try to deal with the body whereas the built-in ones would be TCP up, SSL up, status-code, etc.
