Bug 58121

Summary:	ProxyHTMLMeta seems to ignore all <meta http-equiv="Content-***
Product:	Apache httpd-2	Reporter:	silencer018
Component:	mod_proxy_html	Assignee:	Apache HTTPD Bugs Mailing List <bugs>
Status:	NEW ---
Severity:	normal	Keywords:	FixedInTrunk
Priority:	P2
Version:	2.4-HEAD
Target Milestone:	---
Hardware:	PC
OS:	All

Description silencer018 2015-07-10 06:35:33 UTC

http://httpd.apache.org/docs/2.4/mod/mod_proxy_html.html#proxyhtmlmeta

During my test, when ProxyHTMLMeta is specified,  I found:

1) <meta http-equiv="Content-Type" content="xxx; charset=xxx">  is not added to the response header and the <meta...> tag is also removed from the response body part.

2) <meta http-equiv="Content-Language" content="en-US"> is not added to the response header but the  <meta..> tag is left in the response body.

3) ALl other <meta http-equiv=***> which does not start with "Content-" can be successfully add to the response header.

I want to know is the result correct for test 1) and 2) ? Why Content-Language are not added to the response header ?

Comment 1 Nick Kew 2017-12-16 21:04:20 UTC

(In reply to silencer018 from comment #0)
> http://httpd.apache.org/docs/2.4/mod/mod_proxy_html.html#proxyhtmlmeta
> 
> During my test, when ProxyHTMLMeta is specified,  I found:
> 
> 1) <meta http-equiv="Content-Type" content="xxx; charset=xxx">  is not added
> to the response header and the <meta...> tag is also removed from the
> response body part.

This is correct (and documented, but I'm reviewing the docs).  libxml2 works internally in utf-8, and mod_proxy_html will always output utf-8 unless overridden by ProxyHTMLCharsetOut.

> 2) <meta http-equiv="Content-Language" content="en-US"> is not added to the
> response header but the  <meta..> tag is left in the response body.

Whoops, confirmed, that looks like a bug!  Investigating.  Damn, can't close this bug yet.

Comment 2 Nick Kew 2017-12-16 22:05:48 UTC

Fixed in trunk in r1818457 .