ext/html; charset=UTF-8"%>). After
having specified that, utf8 characters display correctly.
- I also have a configuration problem at the MySQL JDBC driver level. Whereas
the database is configured for utf8, I also need to specify some parameters in
the JDBC url (see
http://confluence.atlass
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom,
On 4/12/2011 4:22 AM, Tomislav Brkljačić wrote:
> After that i added the whole spring distro, ran the test scenarios and
> didn't find any problems.
I guess if that works I just think it's unnecessary because you can
use a filter from somewh
d me a Belgian beer and Andre an American one. :)
>
> (PS there actually are decent American beers)
>
> - -chris
>
I've heard of Corsendonk beer as a fine one. Don't know any American beers
(beside B) :)
--
View this mess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom,
On 4/9/2011 12:53 PM, Tomislav Brkljačić wrote:
> I gave the "add the filter and bunch of Spring jars" method a try and it
> turned out to be a success!
You don't need a "bunch of Spring jars"... just use the one that comes
with Tomcat and be d
Fadil wrote:
unsubscribe
--
|
v
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr..
rs (š,ć,čćžđ ) in the filename.
> I have set the file.encoding=UTF8 and UriEncoding = UTF8 for jvm and inside
> the server.xml.
> Everything works as expected, no anomalies in displaying the filenames of
> the uploaded files.
>
> Situation 2. - client machine, win server 2
Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2fMCAACgkQ9CaO5/Lv0PDa8gCfSrZxjxF4vcEcsHkAqFChnYZ4
> nsYAni7LNi0PeGjgGGhxxZadvQOh6QuY
> =VwYO
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 4/8/2011 11:50 AM, André Warnier wrote:
> Tomislav Brkljačić wrote:
>> The remote machine gives the wrong "result".
>>
>> I wrote on the mailing list of the BPM software, the discussion is still
>> alive.
>>
>> Maybe i could try to force a C
Tomislav Brkljačić wrote:
The remote machine gives the wrong "result".
I wrote on the mailing list of the BPM software, the discussion is still
alive.
Maybe i could try to force a CharacterEncodingFilter filter on tomcat.
Something like
http://www.onthoo.com/blog/programming/2005/07/charactere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom,
On 4/8/2011 11:42 AM, Tomislav Brkljačić wrote:
> The remote machine gives the wrong "result".
Okay. Could you post a LiveHttpHeaders dump of /that/ interaction, too?
> I wrote on the mailing list of the BPM software, the discussion is still
>
illa - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2fHlAACgkQ9CaO5/Lv0PAJpwCeLrK7QVnL8bEkyfXow8Thj6UD
> TpEAoJgmtujwwN+VvvCHQzUHZsf9e2qO
> =9LWc
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom,
On 4/8/2011 4:19 AM, Tomislav Brkljačić wrote:
> Ok, this is what i did.
>
> 1. updated the java runtime so they match on both machines
Not a bad idea, but probably didn't affect anything.
> Tried to run the examples, but still the same result
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 4/7/2011 5:15 PM, André Warnier wrote:
> Christopher Schultz wrote:
> ... (RFC references) ..
>
> Thanks for that post (with the chain of applicable RFCs). I will keep
> that email preciously as a resource for future file upload debugging
>>>> I have a web app deployed to tomcat, and the app has a webform for
>>>> uploading
>>>> attachments.
>>>> Attachments can have funny letters (š,ć,čćžđ ) in the filename.
>>>> I have set the file.encoding=UTF8 and UriEncoding = UTF8 for j
Christopher Schultz wrote:
... (RFC references) ..
Thanks for that post (with the chain of applicable RFCs). I will keep that email
preciously as a resource for future file upload debugging references.
...
Also, to add to the potential OP woes, there is also the fact that some browsers send t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 4/7/2011 12:26 PM, André Warnier wrote:
> What I am saying is that, since you have the same Tomcat version on both
> systems, the code which works differently is unlikely to be in Tomcat
> itself. To my recollection (maybe wrong), Tomcat 6.
the filename.
I have set the file.encoding=UTF8 and UriEncoding = UTF8 for jvm and
inside
the server.xml.
Everything works as expected, no anomalies in displaying the filenames of
the uploaded files.
Situation 2. - client machine, win server 2003
Same webapp as in Situation 1, same tomcat
ments.
>> Attachments can have funny letters (š,ć,čćžđ ) in the filename.
>> I have set the file.encoding=UTF8 and UriEncoding = UTF8 for jvm and
>> inside
>> the server.xml.
>> Everything works as expected, no anomalies in displaying the filenames of
>> the
=UTF8 and UriEncoding = UTF8 for jvm and inside
the server.xml.
Everything works as expected, no anomalies in displaying the filenames of
the uploaded files.
Situation 2. - client machine, win server 2003
Same webapp as in Situation 1, same tomcat configuration in all matters.
But there is aproblem
Hi to all,
this is my scenario and problem.
Situation 1. - local machine, win xp
I have a web app deployed to tomcat, and the app has a webform for uploading
attachments.
Attachments can have funny letters (š,ć,čćžđ ) in the filename.
I have set the file.encoding=UTF8 and UriEncoding = UTF8
On 30/06/2010 16:20, Caldarale, Charles R wrote:
From: Chris Rafferty [mailto:chris.raffe...@sidonis.com]
Subject: RE: FormAuthenticator exception with non-latin (UTF8) user
name
I changed the manager application's web.xml to use FORM
based authentication, added the valve to its contex
> From: Chris Rafferty [mailto:chris.raffe...@sidonis.com]
> Subject: RE: FormAuthenticator exception with non-latin (UTF8) user
> name
>
> I changed the manager application's web.xml to use FORM
> based authentication, added the valve to its context.xml
You really s
to:ma...@apache.org]
Sent: 30 June 2010 12:28
To: Tomcat Users List
Subject: Re: FormAuthenticator exception with non-latin (UTF8) user name
On 30/06/2010 12:22, Chris Rafferty wrote:
> This only occurs when I add the following valve to /conf/context.xml
>
> characterEncoding="UTF-8
On 30/06/2010 12:22, Chris Rafferty wrote:
This only occurs when I add the following valve to /conf/context.xml
Bad idea on a number of levels.
1. That change then applies to *every* context, and will break any that
don't use FORM authentication.
2. The Manager app uses BASIC authen
Hi,
I'm getting the following exception when I try to access the list of
deployed webservices (http://localhost:8080/manager/list) with a user who
has non-Latin characters in their user name:
java.lang.NullPointerException
org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginP
realta wrote:
> I've recently had to upgrade from Tomcat5.5.20 to Tomcat5.5.27. For the main
> functionality of the web application to work it needs to process a UTF8
> encoded cookies to retrieve user customizations. There was no issue with the
> 5.5.20 version, but the 5.5.
I've recently had to upgrade from Tomcat5.5.20 to Tomcat5.5.27. For the main
functionality of the web application to work it needs to process a UTF8
encoded cookies to retrieve user customizations. There was no issue with the
5.5.20 version, but the 5.5.27 version is not processing the
I use a chat servlet deployed in tomcat 5.5.
Because i live in France, i need some special characters like é / à / ç.
When testing with my IDE (netbeans + tomcat 5.5) i've no problem with
these characters, as i use UTF-8.
When serving the HTML canvas page, i declare UTF-8 encoding in the
do
and jdk5 allso using commons.fileupload , when
> > uploading a XML that contains hebrew fonts i can't seem to get it in
> utf8 in
> > the servlet tough JSP is configured to utf8 with :
> > <%@ page language="java" contentType="text/html; charset=UTF-8"
7, Amnon Lahav <[EMAIL PROTECTED]> wrote:
> hi ,
> i'm using tomcat 5.5 and jdk5 allso using commons.fileupload , when
> uploading a XML that contains hebrew fonts i can't seem to get it in utf8 in
> the servlet tough JSP is configured to utf8 with :
> <%@ page langu
hi ,
i'm using tomcat 5.5 and jdk5 allso using commons.fileupload , when
uploading a XML that contains hebrew fonts i can't seem to get it in utf8 in
the servlet tough JSP is configured to utf8 with :
<%@ page language="java" contentType="text/html; charset
Java Development Team wrote:
> I dont know about this either. How do I get access to default servlet
You'll only have a problem if:
- you include static resources
- the static resources are encoded other than with the default platform
encoding
If you need to make changes, the default servlet is
I have used a sevlet filter and translte from ISO8859_1 to UTF8 just works
through all application.
> > 1) there are 20 results for Djavax.servlet.request.encoding in google ^^
> > (but am really not sure this parameter really exists in tomcat)
>
> My bad. I kept the &quo
David Delbecq wrote:
> Hi mark, not at all
>
> 1) there are 20 results for Djavax.servlet.request.encoding in google ^^
> (but am really not sure this parameter really exists in tomcat)
My bad. I kept the "-" in front which, of course, suppressed the
results. The option isn't in the spec and isn'
ot; , it's not a tomcat problem, it's a shell rule :) )
this is even better:
JAVA_OPTS="-Djavax.servlet.request.encoding=UTF-8 -Dfile.encoding=UTF-8
${JAVA_OPTS}"
regards
Mark Thomas a écrit :
> Java Development Team wrote:
>
>> Hi everyone.
>> Iam tryi
Java Development Team wrote:
> Hi everyone.
> Iam trying to change server default enconding from ISO8859_1 to UTF8.
> Till now I found 2 differrent solutions.
> The fisrt one is to use the following in my catalina.sh:
> set JAVA_OPTS=-Djavax.servlet.request.encoding=UTF-8
Never s
Hi everyone.
Iam trying to change server default enconding from ISO8859_1 to UTF8.
Till now I found 2 differrent solutions.
The fisrt one is to use the following in my catalina.sh:
set JAVA_OPTS=-Djavax.servlet.request.encoding=UTF-8 -Dfile.encoding=UTF-8
Putting this line in the start of my
Joacim Turesson wrote:
> I have trouble with UTF-8 and form based login with Tomcat 5.5.12 together
> with Apache 2.0.55 using mod_jk 1.2.15.
See the last section of
http://tomcat.apache.org/tomcat-5.5-doc/config/valve.html
> I have a struts based application that works fine with UTF-8, but the f
Hi!
First of all, Im sorry for my empty mail.
Now to my question.
I have trouble with UTF-8 and form based login with Tomcat 5.5.12 together
with Apache 2.0.55 using mod_jk 1.2.15.
I have a struts based application that works fine with UTF-8, but the form
based login using jdbc realm
50 matches
Mail list logo
