httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Kew <>
Subject Re: [users@httpd] I18N, HTTP 2.0 ?
Date Mon, 20 Oct 2008 14:40:40 GMT
William A. Rowe, Jr. wrote:
> Nick Kew wrote:
>>> So what does the HTML spec have to say?  The <FORM > submission element
>>> does include the accept-charset attribute, perhaps that is what you are
>>> looking for?  Otherwise, if the user agents don't observe RFC 2388 then
>>> you should really take that up with the user agent vendors.
>> This became a (relatively) frequent complaint with mod_proxy_html 2.x, and
>> one of the motivations behind the updates in 3.0.
>> The issue: libxml2 uses utf-8 internally.  When presented with a different charset,
>> mod_proxy_html has to convert (or setup the parser to convert internally), and
>> mod_proxy_html 2.x always generates output as utf-8.
> Right - using an xml parser for sgml has several interesting side effects :)

HTMLparser parses HTML and XHTML.  And, more to the point in real
life, it parses tag-soup.

> So just out of curiosity, the module always emits the charset=utf-8 property
> for the request body content-type?  Tomcat, for example, should parse such
> request bodies with no issue.  Only non-utf-8 aware, custom applications
> that don't a charset-aware parser should fail.

Nope, the module doesn't touch requests.  It only process responses.

Nick Kew

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message