https://bz.apache.org/bugzilla/show_bug.cgi?id=68446
--- Comment #1 from abernal <[email protected]> --- I could not reproduce that a HEAD request sends the body, with httpd built from trunk (commit 6da0450e00, event MPM, Linux). Configuration: ErrorDocument 404 /static/generic.html and ErrorDocument 403 /static/generic.html, with a 53 byte file. A GET to a missing path returns 404 with Content-Length: 53 and the page. A HEAD to the same path returns the same headers, including Content-Length: 53, and no bytes after the headers (I read the raw response from a socket and counted 0 bytes). The same for a 403 caused by a directory without permission. curl -I works without any error. A Content-Length in the answer to HEAD is allowed by RFC 9110, section 9.3.2, as it is the length the GET would have. One thing I saw: with "curl -X HEAD" (instead of -I) curl waits for the 53 bytes that Content-Length announces and ends with a timeout, because the server sends no body. That could look like a problem with the HEAD answer, but it comes from how the request is sent. What I did not test: the 400 case of the report, the bytes written in the access log (%b or %O), and 2.4.x. Could you say how the HEAD request is sent, which httpd version it is, and attach the access log line of such a request? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
