* Disable persistent HTTP connections between Apache mod_proxy and the Hydra backend. This seems to prevent random corrupt output (i.e., pages consisting only of "0").
* Disable persistent HTTP connections between Apache mod_proxy and the Hydra backend. This seems to prevent random corrupt output (i.e., pages consisting only of "0"). It seems that sometimes mod_proxy decides not to forward the request to the backend. For instance, $ curl --head http://hydra.nixos.org/foo.svg normally prints (among other headers) HTTP/1.1 404 Not Found Content-Type: text/html; charset=utf-8 (because /foo.svg doesn't exist), but sometimes it will say HTTP/1.1 200 OK Content-Length: 1 Content-Type: image/svg+xml After such a HEAD request, a subsequent GET request is likely to print "0". It's worth mentioning that Starman's documentation for its ‘--disable-keepalive’ option says: an useful workaround if you run Starman behind a broken frontend proxy that tries to pool connections more than a number of backend workers (i.e. Apache mpm_prefork + mod_proxy). whatever that means. svn path=/configurations/trunk/tud/; revision=34214