Hello,
Sorry for my very late answer!
I took me time to solve the problem basing on what you suggested. In fact,
there are two different ones:
- I use Tiles and I don't specify header in all elements building the final
page (<%@page language="java" contentType="text/html; charset=UTF-8"%>). Af
Thierry Templier wrote:
Hello André,
After having disabled compression at Apache level, things change a bit since now content from database is correctly displayed using
JSTL () but it's still not the case for content of JSP pages. I
have however that at the beginning of JSP pages: <%@page lang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thierry,
On 5/2/2011 4:31 AM, Thierry Templier wrote:
>
Just to be sure, I highly recommend coding your pages like this:
This will ensure that you aren't sending ISO-8859-1 but claiming that
it's UTF-8.
> The content type header is the same and
Hello André,
After having disabled compression at Apache level, things change a bit since
now content from database is correctly displayed using JSTL () but it's still not the case for content of
JSP pages. I have however that at the beginning of JSP pages: <%@page
language="java" contentType="
Hello André,
I made tests in both browsers:
- Firefox 3.6.16 (linux)
- Chrome 11.0.696.57 (linux)
and I have the same behavior.
Thierry
> Additional question : did you try it
> with different browsers ?
-
To unsubscribe, e-ma
Additional question : did you try it with different browsers ?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Thierry Templier wrote:
Hi André,
Thanks very much for your help!
I checked difference between two access:
- Using Apache / modjk / Tomcat that can't display correclty non latin1
characters
- Directly using Tomcat that works fine
Except characters that don't display correctly content are the
Hi André,
Thanks very much for your help!
I checked difference between two access:
- Using Apache / modjk / Tomcat that can't display correclty non latin1
characters
- Directly using Tomcat that works fine
Except characters that don't display correctly content are the same, especially
meta ta
Hello Matteo,
Thanks very much for your answer but I didn't receive the end...
As suggested, I tried both addresses and the result isn't the same. When using
Tomcat directly, everything works fine and when accessing through modjk, I have
problem with non latin1 characters... So I think that it'
Thierry Templier wrote:
Hello,
I developped an application that uses UTF8 encoding since it needs to display
arabic characters. When directly accessing the application from Tomcat,
everything works fine. When I tried to access it through Apache web server and
mod jk, I have problems to displa
t the origin.
If you
-Original Message-
From: Thierry Templier [mailto:temp...@yahoo.fr]
Sent: venerdì 29 aprile 2011 14:33
To: users@tomcat.apache.org
Subject: mojk and utf8 charset problem
Hello,
I developped an application that uses UTF8 encoding since it needs to display
a
Hello,
I developped an application that uses UTF8 encoding since it needs to display
arabic characters. When directly accessing the application from Tomcat,
everything works fine. When I tried to access it through Apache web server and
mod jk, I have problems to display such characters. Utf8 is
12 matches
Mail list logo