-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thorsten,
On 11/27/18 04:48, Thorsten Schöning wrote:
> Guten Tag Christopher Schultz, am Montag, 26. November 2018 um
> 16:07 schrieben Sie:
>
>> web.xml - ---
>> UTF-8
>>
>
> Tested that with Tomcat 9 and this setting fixed my problem
Guten Tag Christopher Schultz,
am Montag, 26. November 2018 um 16:07 schrieben Sie:
> web.xml
> - ---
>
> UTF-8
>
Tested that with Tomcat 9 and this setting fixed my problem the same
as using SetCharacterEncodingFilter. It doesn't work in Tomcat 8.5, I
guess because that simply doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thorsten,
On 11/26/18 08:45, Thorsten Schöning wrote:
> Hi all,
>
> I'm currently testing migration of a legacy web app from Tomcat 7
> to 8 to 8.5 and ran into problems regarding character encoding in
> 8.5 only. That app uses JSP pages and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Justin,
On 1/25/17 12:25 AM, Justin Dang wrote:
> Hi, I have a clean install of an older version of Tomcat (8.0.24).
> I have noticed when a character is encoded in the URL, Tomcat fails
> to return the URL requested. I've noted this same request
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 8/24/16 3:46 PM, James H. H. Lampert wrote:
> On 8/24/16, 12:36 PM, Mark Thomas wrote:
>
>> At a guess, something in the web application is using the
>> platform default encoding rather than an explicit encoding. Given
>> that the Linux
On 8/24/16, 12:36 PM, Mark Thomas wrote:
At a guess, something in the web application is using the platform
default encoding rather than an explicit encoding. Given that the Linux
box is OK, it looks like the app should be explicitly using UTF-8
everywhere.
Based on a response I got on the
On 24/08/2016 17:43, James H. H. Lampert wrote:
> Ladies and Gentlemen of the Tomcat and Midrange-Java communities:
>
> We're having a weird problem with character encoding in a Tomcat webapp.
>
> We've added an interface to GMail to our webapp, and we've got, just for
> our own development,
The Microsoft characters are encoded in CP-1252
(http://en.wikipedia.org/wiki/Windows-1252).
However, if the problem is the database-driven content, then you also need to consider
the encoding that the dB is using. For example, MySQL might by default use latin1
(ISO-8859-1), so your data
On 27/08/2010 18:23, laredotornado wrote:
Hi,
I'm using Tomcat 6.0.26. I'm noticing that when our JSPs pages are served,
we frequently have ?s where apostrophes should be. We think this is
because the database-driven content contains the Microsoft style apostrophe.
[wince]
My
Very nice work, Thank you for the sharing.
On Fri, Feb 12, 2010 at 11:23 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
My company recently decided to alter our password complexity
requirements for our webapp, and I got to
: Character encoding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| You say:
| Tomcat does not use any environment variables. The only settings that
| affect the interpretation of the URI are the URIEncoding and
| useBody... settings on the Connector. Are you using more than one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| Chris, I finally found it.
| My server.xml was not correctly configured. My fault.
|
| Again, thank you all for your help.
No problem. Would you mind explaining for the group what the actual
problem was, and what the solution was?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| I'm having difficulties trying to decode URI parameters into UTF8.
:(
| When I moved the application
| to linux (debian etch) I found out it was not working.
We run on Linux as well. TC 5.5.23, Java 1.5.0_11. We have configured
etch (works fine in windows xp).
Many thanks.
- Original Message
From: Christopher Schultz [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, June 18, 2008 3:56:13 PM
Subject: Re: Character encoding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch
nch wrote:
Thanks, Christopher.
This doesn't work either.
Could you give an example of such a UTF-8 encoded URI ?
(and tell us what it should be decoded to)
Thanks
-
To start a new topic, e-mail: users@tomcat.apache.org
To
PM
Subject: Re: Character encoding
nch wrote:
Thanks, Christopher.
This doesn't work either.
Could you give an example of such a UTF-8 encoded URI ?
(and tell us what it should be decoded to)
Thanks
-
To start a new topic, e
- Original Message -
From: André Warnier [EMAIL PROTECTED]
Could you give an example of such a UTF-8 encoded URI ?
(and tell us what it should be decoded to)
Thanks
Andre have a look here... its not url encoding, thats something different
It about being able to store japanese and
- Original Message -
From: nch [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, June 18, 2008 5:09 PM
Subject: Re: Character encoding
There it goes.
I have a form that has an input field named query. I type piraña an
submit the form using the GET
- Original Message -
From: Johnny Kewl [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, June 18, 2008 6:26 PM
Subject: Re: Character encoding
- Original Message -
From: nch [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| This doesn't work either.
:(
| I removed the useBodyEncoding property, as you suggested, from the
| Connector element, but the URI parameter coming in the request is
| still being decoded into ISO-8859-1 instead of UTF-8.
How do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| I have a form that has an input field named query. I type piraña
| an submit the form using the GET method. I can see the browser has
| encoded this parameter into the URI as query=pira%C3%B1a
Is this a correct UTF-8 encoding of
]
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, June 18, 2008 7:25:03 PM
Subject: Re: Character encoding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| I have a form that has an input field named query. I type piraña
| an submit the form using the GET method. I can see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| - I do remote debugging through Eclipse to both tomcat on windows
| (same machine as eclipse, though) and tomcat on debian.
Okay, remote debugging should not affect the server, but I'm still
wondering if the server.xml you think
Chris, thanks for your help.
Please, see my comments bellow.
Kind regards.
- Original Message
From: Christopher Schultz [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, June 18, 2008 9:42:21 PM
Subject: Re: Character encoding
-BEGIN PGP SIGNED
tomcat read them indirectly through it??
Cheers
- Original Message
From: Christopher Schultz [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, June 18, 2008 9:42:21 PM
Subject: Re: Character encoding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| But, if the URL is allways encoded in the same way and tomcat does
| not receive any other information on what the resulting character
| encoding should be. Why do I get different values from tomcat?
Because the servers are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
nch wrote:
| You say:
| Tomcat does not use any environment variables. The only settings that
| affect the interpretation of the URI are the URIEncoding and
| useBody... settings on the Connector. Are you using more than one
| connector? Are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lightbulb,
lightbulb432 wrote:
POST requests always use the request's body encoding, which is
specified in the HTTP header (and can be overridden by using
request.setCharacterEncoding). Some broken clients don't provide
the character encoding
That was a really great set of answers, thanks! These follow-ups are somewhat
off-topic to Tomcat, but you really know this stuff well so I hope you don't
mind addressing them:
POST requests always use the request's body encoding, which is specified
in
the HTTP header (and can be overridden
Lightbulb,
lightbulb432 wrote:
Why is the URIEncoding attribute specified on the connector rather than on a
host, for example?
Because the host doesn't handle connections... the connectors do.
Does this mean that the number of virtual hosts that can
listen on the same port on the same box
Hello Mark
Mester József wrote:
Ok. Let's see my problem.
I have a form with text input box. I type Árvíztűrő tükörfúrógép and I get
ÃrvÃztűrÅ tükörfúrógép
I have tested this with the latest 5.5.x source and it works correctly
(there haven't been any encoding related fixes since
Mester József wrote:
Hello Mark
Ok. Let's see my problem.
I have a form with text input box. I type Árvíztűrő tükörfúrógép and I get
ÃrvÃztűrÅ tükörfúrógép
Beautiful isn't it?
I have tested this with the latest 5.5.x source and it works correctly
(there haven't been any
Hello Mark
This is unlikely to help you and may be read-only on your JVM.
You don't say what doesn't work but generally the following is required:
set URIEncoding=UTF-8 on the connector
set the the correct response encoding on every response (you can do
this per page or use a filter to do this
export CATALINA_OPTS=-Dfile.encoding=UTF-8
On 12/12/06, Mester József [EMAIL PROTECTED] wrote:
Hi
I have some problem with character encoding. I have found a page (
http://junlu.com/msg/1132.html ) and on this page there is a direction:
2.
In the Catalina.bat (windows) catalina.sh (linux)
THANKS, that URIencoding property of HTTP connector was source of GET
problems
I tried to remove filter after that, but POST requests stop working. So
ive instaled filter back.
Now I have working both GET and POST. Aleluja...
d.
Anyway its
On Mon, 14 Aug 2006 22:40:27 +0200, Mark Thomas
On 4/3/06, Nigel Blake [EMAIL PROTECTED] wrote:
Problem : Creating a URL type with parameters that have a space
between them causes an IOException in a javabean when called from
Tomcat 5.0.0.27 on a Unix installation. Using the same bean and JSP
code causes no problem when invoked on the same
java.net.URLEncoder.encode
-Original Message-
From: Nigel Blake [mailto:[EMAIL PROTECTED]
Sent: Monday, April 03, 2006 5:43 PM
To: users@tomcat.apache.org
Subject: Character Encoding : Unix vs Windows
Problem : Creating a URL type with parameters that have a space between
them causes
Notice: The information contained in this e-mail message and/or attachments to
it may contain confidential or privileged information. If you are not the
intended recipient, any dissemination, use, review, distribution, printing or
copying of the information contained in this e-mail message
Please don´t send more emails I´m not tomcat user
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Enviado el: Miércoles, 19 de Octubre de 2005 04:20 a.m.
Para: Tomcat Users List
Asunto: RE: Character Encoding -ISo-8859-1 Vs UTF-8 Vs GBK
Notice: The information
Hi,
In Europe we have lots of languages. I don't think it's true that UTF-8 can
handle european character very well.There is a list in the net (I don't know
here) with the other ISO encoding for other languages.
AF
Citando David Delbecq [EMAIL PROTECTED]:
Hi,
UTF-8 can handle european
UTF-8 (8-bit Unicode Transformation Format) is a lossless,
variable-length character encoding for Unicode created by Ken Thompson
and Rob Pike. It uses groups of bytes to represent the Unicode standard
for the alphabets of many of the world's languages. UTF-8 is especially
useful for transmission
Sorry, my mistake! I thought we were speaking about something else...
AF
Citando Peter Crowther [EMAIL PROTECTED]:
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
I don't think it's true
that UTF-8 can handle ALL european character very well.
If it can't, the Unicode consortium
42 matches
Mail list logo
