sh
> Date: Tue, 26 Mar 2013 16:12:12 -0400
> From: ch...@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: Encoding Problem
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Ayush,
>
> On 3/26/13 5:0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ayush,
On 3/26/13 5:07 AM, Cool Techi wrote:
> encodingFilter
> org.springframework.web.filter.CharacterEncodingFilter
>
>
> encoding UTF-8
> forceEncoding
> true
I would highly recommend against setting forceEncoding=true... this
will ca
This is unfortunately happening in our production server and not on or local
servers, hence debugging has become more difficult.
On local servers everything is working fine, both POST and GET requests.
Regards,
Ayush
> Date: Tue, 26 Mar 2013 14:16:24 +0400
> Subject: Re: Encoding P
What kind of request fails, POST or GET or both?
>
> POST is the one in question currently, will test GET.
>
> 3. Have you read the character encodings page of Tomcat FAQ?
>
> Yes
>
> Regards,
> Rohit
>
>> Date: Tue, 26 Mar 2013 13:14:19 +0400
>> Subj
is the one in question currently, will test GET.
3. Have you read the character encodings page of Tomcat FAQ?
Yes
Regards,
Rohit
> Date: Tue, 26 Mar 2013 13:14:19 +0400
> Subject: Re: Encoding Problem
> From: knst.koli...@gmail.com
> To: users@tomcat.apache.org
>
> 20
2013/3/26 Cool Techi :
>
> We are working with multiple languages and Korean being one
> of them, in our application we have set up encoding both at tomcat level
> and also spring filter for encoding, but for some reason when we do a
> request.getParameter in our Struts2 action class we re
davefu wrote:
Hi, this is my setup:
- Debian Lenny
- Tomcat 5.5
- Postgres 8.3
I'm running an app which is failing everytime it tries to get some data from
the DB with characters like [ÁÉÍÓÚáéíóú]. By "failing" I mean the
application isn't showing the data it should when Tomcat throws querys
The XLS file is not encoded using the expected encoding scheme (iso-latin-1,
according to this post). Simply expecting the file to be encoded in such a
way (or telling tomcat to expect it) does not make it so. You must save the
file using the expected encoding, or you can translate it if you know
Mark Thomas wrote:
Can you provide the smallest possible servlet/JSP that doesn't work?
At a guess running in debug mode is fixing/working around some other
issue that is the root cause of the problem.
Mark
I am using tapestry, so I can not really deliver anyhting else than a
tapestry page /
Can you provide the smallest possible servlet/JSP that doesn't work?
At a guess running in debug mode is fixing/working around some other
issue that is the root cause of the problem.
Mark
Ron Piterman wrote:
> now also when both are using the symlink at /home/ron/tomcat, running
> tomcat in norma
now also when both are using the symlink at /home/ron/tomcat, running
tomcat in normal mode (without debugging) gives me wrong encoding...
?
Ron Piterman wrote:
Here are both commands, as listed by ps (i broke them to make reading
easier):
>> first the normal tomcat:
>>
/usr/java/jre/bin/
Here are both commands, as listed by ps (i broke them to make reading
easier):
>> first the normal tomcat:
>>
/usr/java/jre/bin/java
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/usr/java/tomcat/conf/logging.properties
-Djava.endorsed.dirs=
12 matches
Mail list logo