On Tue, Aug 30, 2011 at 3:18 PM, Eric Covener
<covener@xxxxxxxxx> wrote:
It's tuff baked into the core binary, httpd. Note that many dynamic
responses can't be satisfied as range requests, so maybe your "/" is
such a response.
Hi eric,
sorry i was referring to the compiled-in modules, e.g:
Compiled in modules:
core.c
mod_authn_file.c
mod_authz_host.c
mod_log_config.c
mod_logio.c
mod_expires.c
mod_headers.c
worker.c
http_core.c
mod_mime.c
mod_dir.c
mod_rewrite.c
mod_so.c
or is it in the "core.c"??
my servers are currently throwing the HEAD requests away as 404's ,e.g:
2011-08-30 15:38:20 10.107.23.207 steve.test HEAD / HTTP/1.1 404 - 229 - - -
So guess its down to that. However modifying the request to be a GET for a valid resource still didn't trigger the memory consumption behaviour.
Steve
