Health check

The handler answers GET /_dusk/health itself with 200 and {"status":"ok"} (HEAD gets no body) and Cache-Control: no-store. It runs before the host check, CSRF and your middleware, so a load balancer that probes by IP address and a rate limiter in front of everything else do not break it. It says the process is up and can answer a request, nothing about your database. healthPath moves it, false turns it off. The path is not below base.