Bug #349
closedmod_proxy ignores / doesn't pass trough 'Content-Length' for HEAD requests
Description
lighttpd with enabled mod_proxy does not pass trough the Content-Length if queried via a HEAD-request.
testing scenario:
lighttpd 1.4.6 @ 127.0.0.1:80, mod_proxy loaded
mod_proxy configuration:
proxy.server = ( "" => ( ( "host" => "127.0.0.1", "port" => 8080 ) ) )
proxy.debug = 1
lighttpd 1.4.6 @ 127.0.0.1:8080, no modules loaded
$ lynx -dump -head http://localhost/index.html | grep Content-Length
Content-Length: 0
$ wc -c index.html
23 index.html
See the attached strace outputs. It's working for GET requests, but fails on HEAD requests.
I don't see something critical in the proxy.debug output:
2005-10-30 15:43:52: (mod_proxy.c.1063) proxy - start
2005-10-30 15:43:52: (mod_proxy.c.1099) proxy - ext found
2005-10-30 15:43:52: (mod_proxy.c.1142) proxy - used fair balancing
2005-10-30 15:43:52: (mod_proxy.c.1219) proxy - found a host 127.0.0.1 8080
2005-10-30 15:43:52: (mod_proxy.c.379) connect delayed: 7
2005-10-30 15:43:53: (mod_proxy.c.978) proxy: fdevent-out 1
2005-10-30 15:43:53: (mod_proxy.c.779) proxy - connect - delayed success
2005-10-30 15:43:53: (mod_proxy.c.945) proxy: fdevent-in 4
2005-10-30 15:43:53: (mod_proxy.c.620) proxy - have to read: 248
2005-10-30 15:43:53: (mod_proxy.c.945) proxy: fdevent-in 4
2005-10-30 15:43:53: (mod_proxy.c.620) proxy - have to read: 0
Files
Updated by jan about 19 years ago
- Status changed from New to Fixed
- Resolution set to fixed
fixed in changeset r862
Also available in: Atom