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
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 receive only ??.
Tomcat Encodin
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
ection to
LATIN1. The logs are good on both sides this time, but still the app is not
receiving the data on screen. Seems like somehow the query is not reaching
sane (due to bad encoding) to postgres, or postgres is not sending it back
to tomcat.
If I set system locale to ISO-8859-1, the data is dis
2010/1/22 François Duvalier :
> Hi,
>
> When I execute this command:
>
> curl -XGET -i http://localhost:8080/app/rs/system/EN/foo%2Fbar
>
> I receive a 400 BAD REQUEST.
>
> However if I deploy the app to Jetty, the command will work fine.
>
> Question: Is there a way to configure tomcat to behave l
Hi,
When I execute this command:
curl -XGET -i http://localhost:8080/app/rs/system/EN/foo%2Fbar
I receive a 400 BAD REQUEST.
However if I deploy the app to Jetty, the command will work fine.
Question: Is there a way to configure tomcat to behave like jetty with
regards to percent-encodings in
Problem solved... but i still have some doubts :p
This was my solution:
1. Remove this next lines of all JSPs (some had, others didn't)
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
2. In web.xml added a CharsetFilter of Spring
André Warnier wrote:
>[...]
>Now, I should add that using [ and ] in URL's is not really something I would
>recommend, if only for legibility reasons. It will always make people wonder
>if what they're seeing in the logfile is normal, or if it's some programming
>syntax which "escaped" there.
>
Jesse Klaasse wrote:
[...]
Good.
Now, I should add that using [ and ] in URL's is not really something I
would recommend, if only for legibility reasons. It will always make
people wonder if what they're seeing in the logfile is normal, or if
it's some programming syntax which "escaped" ther
Jesse Klaasse wrote:
[...]
Good.
Now, I should add that using [ and ] in URL's is not really something I
would recommend, if only for legibility reasons. It will always make
people wonder if what they're seeing in the logfile is normal, or if
it's some programming syntax which "escaped" ther
André Warnier wrote:
>It would appear (from the logs), that there is some double-encoding of the URI
>going on.
>[snip]
>But, if somewhere along the line, a piece of code was receiving the encoded
>URI "http://.../test%5Bbrackets%5D.jsp";, and decided to re-encode it again
>using the "% hex hex
aasse [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2008 2:14 AM
To: users@tomcat.apache.org
Subject: URL encoding problem IIS6 / JK1.2.25 / Tomcat 5.5.20
I have recently migrated a production server from IIS5 / Resin 3.0.14 to
IIS6 / JK1.2.25 / Tomcat 5.5.20. Now, there seems to be a problem
Jesse Klaasse wrote:
[snip]
Now, we try the whole link through the JK connector:
http://localhost/webapp/test[brackets].jsp
This doesn't work, and results in a 404 error (appearing in both IIS and
Tomcat's log as test%5Bbrackets%5D.jsp, Tomcat with a 404, IIS with a
200).
Thanks for the exc
I have recently migrated a production server from IIS5 / Resin 3.0.14 to
IIS6 / JK1.2.25 / Tomcat 5.5.20. Now, there seems to be a problem with
the URL translation from IIS to Tomcat.
I have this file in a webapp, called test[brackets].jsp.
When I try http://localhost:8080/webapp/test[brackets].js
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
Joseph S wrote:
> Christopher Schultz wrote:
>
>> Setting the encoding of the response is sometimes necessary when the
>> browser (stupidly, IMO) elects not to send the charset being used to the
>> server.
>>
> It isn't the browser's fault, its
Christopher Schultz wrote:
Setting the encoding of the response is sometimes necessary when the
browser (stupidly, IMO) elects not to send the charset being used to the
server.
It isn't the browser's fault, its the spec's fault. See
https://bugzilla.mozilla.org/show_bug.cgi?id=289060#c8
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark and Joe,
Mark Thomas wrote:
> Joseph Shraibman wrote:
>> Mark Thomas wrote:
>>
>>>request.setCharacterEncoding("UTF-8");
>>
>> Is this always safe? For responses I can (and do) check the
>> accept-charset request [header], but I can't fi
Most browsers will encode the request the same as the page it came from. This
is true for POST variables. I'm not sure about GET query variables.
In the past I found some websites explaining this hidden feature, but don't
have the time to search again.
Ronald.
On Thu Aug 16 20:25:18 CEST 2007
Joseph Shraibman wrote:
> Mark Thomas wrote:
>
>>request.setCharacterEncoding("UTF-8");
>
> Is this always safe? For responses I can (and do) check the
> accept-charset request paramater, but I can't figure out how to tell
> what the request encoding should be.
It should be reasonable u
Joseph Shraibman wrote:
> This is an old problem. See
> https://bugzilla.mozilla.org/show_bug.cgi?id=18643
> https://bugzilla.mozilla.org/show_bug.cgi?id=7533
>
> Firefox and MSIE use a magic _charset_ paramater, but I can't use it
> because if I call request.getParamater("_charset_") I can't set
This is an old problem. See
https://bugzilla.mozilla.org/show_bug.cgi?id=18643
https://bugzilla.mozilla.org/show_bug.cgi?id=7533
Firefox and MSIE use a magic _charset_ paramater, but I can't use it
because if I call request.getParamater("_charset_") I can't set the
encoding after that!
Anyw
Mark Thomas wrote:
request.setCharacterEncoding("UTF-8");
Is this always safe? For responses I can (and do) check the
accept-charset request paramater, but I can't figure out how to tell
what the request encoding should be.
--
Try this then - this is my standard character encoding index.jsp test.
<%@ page contentType="text/html; charset=UTF-8" %>
Character encoding test page
Data posted to this form was:
<%
request.setCharacterEncoding("UTF-8");
out.print(request.getParameter("
POST
Mark Thomas wrote:
Joseph S wrote:
When I did that my content displayed correctly, but on form submission
it got corrupted.
POST or GET?
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-m
Joseph S wrote:
> When I did that my content displayed correctly, but on form submission
> it got corrupted.
POST or GET?
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
Fo
Nathan Hook wrote:
A few things...
First, what type of apostrophe are you using? Are you using a typical
ascii apostrophe (') or are you using the Microsoft slanted apostrophe
that comes out of word documents (′)?
It's ’
Here are two links that describe the problem:
http://www.cs.tut.
terChain.doFilter(request, response);
}
}
Finally, I would also set the meta header on the jsp page to be utf-8 just
to be complete...
Regards...
Original Message Follows
From: Joseph S <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List"
To: Tomcat Users List
Subject
My problem is this:
One of my pages with an apostrophe was not displaying properly, so I
added to my jsp:
<%@ page contentType="text/html; charset=UTF-8"%>
When I did that my content displayed correctly, but on form submission
it got corrupted.
You can view the problem here:
http://b.tupa
Thanks for all your help. Here's some more data and an update:
1) The jsp is basically displaying unicode strings from the db. So,
there is no other data other than a directive to print the string from
the db.
2) Running a direct query from the db shows the string correctly. The
db is mysql.
If your JSP page is being included from another servlet, then it won't be
allowed to set the content-type (or charset) of the response. Just a wild
guess here :).
The HTTP/1.1 RFC states that the character encoding of the headers is
iso-8859-1. That is why Tomcat doesn't provide an option to
> From: Enrico Donelli [mailto:[EMAIL PROTECTED]
> Subject: Re: Response encoding problem
>
> I don't know if this helps, but I had a similar problems once, and it
> was caused by a filter which was reading a parameter from the request.
> This first access set the encodin
I don't know if this helps, but I had a similar problems once, and it
was caused by a filter which was reading a parameter from the request.
This first access set the encoding to 8859-1, overriding all my
following settings.
I would start from this ... hope this helps.
Good luck!
Enrico
On 18/1
Hi - I'm trying to show utf-8 data in the browser from my jsp page.
When the page renders, its character encoding is iso-8859-1, according
to the browser. The http
response headers have the same encoding (iso-8859-1).
Here's what's been done thus far:
1) meta tag set as follows:
2) jsp page e
From: "V. Karthik Kumar"
Date: 2004-08-31 19:32:43
Message-ID: 1093980042.5241.7.camel () ATLAS
use:
response.setCharacterEncoding("Whatever"); <-- internally, this is what
the tags translate to...
Before u carry on with out.print() statements...
And one more thing.. there is an
you reuse pages from other sources
and want to store every page in one encoding.
BTW, this doesn't appear to be a tomcat question...
HTH,
Tim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, May 01, 2006 4:46 AM
To: Tomcat Users List
Subject: Encodi
Hi,
Gurus I am doing an xls & text upload in parallel and inserting data into
data base.
When I am viewing data I find the data through txt upload is comming
correct and through xls upload is comming wrong.
I am doign this with thease four character Š š Ž ž I am using iso-latin-1
encoding. My ma
Hi Gurus ,
I am facign a typical problem regarding the special characeter Š š Ž ž
which get uploaded into the database in differently when uploaded throgh
windows environment and my UNIX environment .
I upload data using 1. TXT and 2. XLS file , when on window setup it
uplaoded the uploaded dat
o be in the catalina.home and
catalina.base parameters -
/home/ron/tomcat is a symlink to /usr/java/tomcat/
why should that make a difference ?
will try to change that and see what happens...
(will be back after the commercials :) )
Cheers,
Ron
Ron Piterman wrote:
Hi all,
I have this strange encodi
cat is a symlink to /usr/java/tomcat/
why should that make a difference ?
will try to change that and see what happens...
(will be back after the commercials :) )
Cheers,
Ron
Ron Piterman wrote:
Hi all,
I have this strange encoding problem with tomcat 5.5.12 serving
tapestry pages:
when I star
/ron/tomcat
>> -Djava.io.tmpdir=/home/ron/tomcat/temp
>> org.apache.catalina.startup.Bootstrap start
>>
>> ---
>>
>> Now the only difference seems to be in the catalina.home and
>> catalina.base parameters -
>>
>> /home/ron/tomcat is a symlink to /usr/j
d that make a difference ?
will try to change that and see what happens...
(will be back after the commercials :) )
Cheers,
Ron
Ron Piterman wrote:
Hi all,
I have this strange encoding problem with tomcat 5.5.12 serving
tapestry pages:
when I start tomcat using the startup.sh script, my tapest
rence seems to be in the catalina.home and
catalina.base parameters -
/home/ron/tomcat is a symlink to /usr/java/tomcat/
why should that make a difference ?
will try to change that and see what happens...
(will be back after the commercials :) )
Cheers,
Ron
Ron Piterman wrote:
Hi all,
I have this
Hi all,
I have this strange encoding problem with tomcat 5.5.12 serving tapestry
pages:
when I start tomcat using the startup.sh script, my tapestry pages are
served with something wrong along the encoding pipeline, so some
"special" characters like ä or ß are encoded wrong.
wh
48 matches
Mail list logo
