On 7/8/2014 2:52 AM, Konstantin Kolinko wrote:
2014-07-07 21:07 GMT+04:00 Terence M. Bandoian <tere...@tmbsw.com>:
On 7/5/2014 6:36 PM, André Warnier wrote:
I agree with André about the difficulties of debugging character encodings.
A couple of things you might check are the character encodings of the page
and the form. The character encoding of the page may be set with the
Content-type meta tag:
<meta http-equiv=ontent-type" content="text/html;charset=UTF-8"/>
Setting explicit value for "content" attribute like that is risky. The
value must match the Content-Type HTTP header produced by web server.
If they do not match, some browsers ignore both and start guessing the
encoding.
I usually write it as
<%@ page contentType=ext/html; charset=UTF-8" %>
...
<META http-equiv=ontent-type" content="<%=response.getContentType() %>">
Best regards,
Konstantin Kolinko
Hi, Konstantin-
With JSP pages, I use contentType attribute of the page directive as
well but didn't think to include it in my reply. Thanks for pointing it
out.
-Terence Bandoian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
