On Mar 27, 2008, at 7:51 AM, Andy Stevens wrote:
My HTML serializer is configured with <encoding>UTF-8</encoding> and
the page includes a
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
tag in the <head>. However, where previously (on WAS 5) the app was
returning
Content-Type: text/html
in the response headers, I'm now getting
Content-Type: text/html; charset=iso-8859-1
under WAS 6. It looks like the app server is "helpfully" setting a
default charset when none is present.
Now, the HTML serializer must be setting the content type to text/html
(as opposed to text/xml or any other mime type other serializers might
use). Is it possible to have it also include the encoding,
Yes it is possible - and recommended:
<map:serializer name="html" mime-type="text/html; charset=utf-8" ...>
<encoding>UTF-8</encoding>
</map:serializer>
though, as
I assume if there's one explicitly specified in the header WAS 6 will
leave it alone?
Yes, I think it should do so.
Vadim
Some configuration setting other than the <encoding>, maybe?
Andy.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
