Hi, which part of an Apache/mod_perl setup is responsible for extracting META tags from generated HTML and adding them as HTTP headers (even with PerlSendHeaders Off)? In the case of META NAME='Blah' tags, it adds X-Meta-Blah headers, which are harmless but probably mostly a waste of bandwidth. But in the case of META HTTP-EQUIV tags, it adds non-X headers without caring about existing headers, often leading to double headers, which may also conflict:
shell> lwp-request -sued http://www.apache.org/ GET http://www.apache.org/ 200 OK Cache-Control: max-age=86400 Connection: close Date: Fri, 18 Jan 2002 23:54:30 GMT Accept-Ranges: bytes Server: Apache/2.0.28 (Unix) Content-Length: 7810 Content-Type: text/html Content-Type: text/html; charset=iso-8859-1 Expires: Sat, 19 Jan 2002 23:54:30 GMT Title: Welcome! - The Apache Software Foundation X-Meta-Author: ASF X-Meta-Email: [EMAIL PROTECTED] The way I understand the HTTP spec, multiple Content-Type headers are illegal, and even if not, they certainly can cause trouble. I'm not sure whether the cause for this on the apache.org site is the same as on my test server, but the result is pretty much the same.
