[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#381570: HEAD does not serve <meta http-equiv> headers

Package: apache2
Version: 2.0.55-4
Severity: minor

RFC 2616 says:

   "The metainformation contained in the HTTP headers in response to
   a HEAD request SHOULD be identical to the information sent in
   response to a GET request."

This is not the case in apache2 (up to and including 2.2.3). If
I fire off a GET request, I get the HTTP response headers, plus the
ones added by the CGI or <meta http-equiv> for static files. If
I just fire a HEAD request, only the apache-generated headers are
served. It seems as if apache2 does not actually look at the
file/content to serve, it just provides the meta information (like
size), along with some defaults (text/html).

lapse:~> (HEAD http://martin-krafft.net/phd/;
          GET -esd http://martin-krafft.net/phd/) \
            | egrep '^(..[[:upper:]]|Content-Type)' 
HEAD http://martin-krafft.net/phd/
Content-Type: text/html
GET http://martin-krafft.net/phd/
Content-Type: text/html
Content-Type: application/xhtml+xml; charset=utf-8

I am only making this a minor bug because the RFC only says SHOULD.
Damn RFC. :)

Please do not send copies of list mail to me; I read the list!
 .''`.     martin f. krafft <madduck@debian.org>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system

Attachment: signature.asc
Description: Digital signature (GPG/PGP)

Reply to: