generate a lot of errors. I won't include
the whole stack trace here, but it stems from:
org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
'request-character-encoding' not found.
I've filed [Eclipse Bug
543377](https://bugs.eclipse.org/bugs/show_bug.cgi?id=5433
-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 th
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 im
-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 ap
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 declares all of those to be stored in
UTF-8, does really do so :-), and declares a HTTP-Content type of
"
Thanks Mark! Here it is:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60769
On Tue, Feb 21, 2017 at 9:49 PM, Mark Thomas wrote:
> On 18/02/2017 16:32, Lazar Kirchev wrote:
> > I noticed something else strange. If in an jspx file I declare one and
> > the same encoding (in my case Windows-1252)
On 18/02/2017 16:32, Lazar Kirchev wrote:
> I noticed something else strange. If in an jspx file I declare one and
> the same encoding (in my case Windows-1252) in both the XML prolog and
> the page directive pageEncoding property, on Tomcat 8.5.11 I get the
> error message:
> "Page-encoding specif
I noticed something else strange. If in an jspx file I declare one and the
same encoding (in my case Windows-1252) in both the XML prolog and the page
directive pageEncoding property, on Tomcat 8.5.11 I get the error message:
"Page-encoding specified in XML prolog (UTF-8) is different from that
spe
Hello,
According to the JSP 2.3 spec,
section 3.3.4 (Declaring page encodings):
"It is also a translation-time error to name different encodings in the
prolog / text declaration of the document in XML syntax and in a JSP
configuration element matching the document. It is legal to name the same
enc
.pdf
>
>
> I've reviewed this wiki page:
>
>
> https://wiki.apache.org/tomcat/FAQ/CharacterEncoding
>
>
> And it seems to imply that I shouldn't have to do anything, and the
> URL request should return properly.
>
>
> So my question is, what
estion is, what do I need to configure in Apache Tomcat to handle
the character encoding request like IIS does?
only work with the value you've got there...
don't try to mess with that! :)
FWIW, the system properties of each JVM are somewhat interesting, but
probably won't help you debug anything. It might not even fix anything.
Every HTTP request/response is defined to have a character encoding:
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 Mid
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,
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, testing, and production use, instances
o
set request and response character encoding
I think what Chris is saying is that you don't need to do any coding
with the filter, just configure it.
*Thanks and RegardsAkshat Tandon*
On Tue, Feb 16, 2016 at 8:13 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
Thanks Chris for the response,
Basically we don't want to do coding around the filter as it will also
bring us an additional overhead of maintaining the code and follow the
quality process , Ideally we want say some setting to say in server.xml to
set request and response character enc
Akshat,
On 2/16/16 7:08 AM, Akshat Tandon wrote:
> We need to set tomcat 8.0.20 container character encoding of request and
> response to UTF-8 intead of ISO-8859-1 ,
>
> What is the setting for the same ?
>
> We tried setting as mentioned below ,
> https://wiki.
We need to set tomcat 8.0.20 container character encoding of request and
response to UTF-8 intead of ISO-8859-1 ,
What is the setting for the same ?
We tried setting as mentioned below ,
https://wiki.apache.org/tomcat/FAQ/CharacterEncoding#Q1 But that requires
creating filter etc .
Is there
> FYI: The same issue reported against 5.5.35:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=52579
>
> Thank you for your research. I think you are right. Though I am not
> sure how much this can be fixed in Tomcat now.
Thank you for your responses.
We were able to find the reason for the
cc: dev
2012/1/23 kitagawa :
>>
>> While developing using ubuntu 11.04, tomcat 6.0.33 and java 1.5 I ran
>> into a problem after setting the character encoding filter for
>> requests.
>> When posting a request, the value of any field with only a single
>> cha
Thank you for your response
I read the FAQ and wasn't able to find a solution to the problem.
I researched it some more and found a bug in Java 1.5 in
java.nio.charset.Charset.decode() that might be the cause.
A ticket was submitted regarding a similar problem to sun in 2004
http://bugs.sun.com/b
2012/1/16 kitagawa :
> Hi, I'm new to this but please direct me if I'm posting to the wrong list.
>
> While developing using ubuntu 11.04, tomcat 6.0.33 and java 1.5 I ran
> into a problem after setting the character encoding filter for
> requests.
> When posting a req
Hi, I'm new to this but please direct me if I'm posting to the wrong list.
While developing using ubuntu 11.04, tomcat 6.0.33 and java 1.5 I ran
into a problem after setting the character encoding filter for
requests.
When posting a request, the value of any field with only a single
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 9/1/2011 3:00 PM, David Wall wrote:
> Thanks for all the tips and ideas!
If you had already read this:
http://wiki.apache.org/tomcat/FAQ/CharacterEncoding
...and it didn't help, we welcome any suggestions. Feel free to make
any editions y
You are right about the encoding of the .java file in Eclipse. I tried
in 'vi' and sure enough the codes are in there correctly. Interesting
that Eclipse opened the .jsp file and showed it nicely, but the .java
file was not. I couldn't do the properties, though, since these files
are not par
2011/9/1 David Wall :
> Thanks for the ideas, Mark, but it's still the same undesirable result.
>
> On 9/1/2011 6:58 AM, Mark Thomas wrote:
>>
>> I suspect you need:
>> <%@ page pageEncoding="UTF-8" %>
>> at the start of your JSP.
>>
>> .java files are written using UTF-8 by default so if what you
Thanks for the ideas, Mark, but it's still the same undesirable result.
On 9/1/2011 6:58 AM, Mark Thomas wrote:
I suspect you need:
<%@ page pageEncoding="UTF-8" %>
at the start of your JSP.
.java files are written using UTF-8 by default so if what you see there
is wrong then the original .jsp
On 01/09/2011 03:41, David Wall wrote:
> I'm trying to track down a character encoding issue that I've been
> having, but don't really understand. Hopefully one of you will know what
> the answer is.
I suspect you need:
<%@ page pageEncoding="UTF-8" %>
at
I'm trying to track down a character encoding issue that I've been
having, but don't really understand. Hopefully one of you will know what
the answer is.
I am using CKEditor to generate some user-specified HTML. CKEditor
offers an "insert special character" function
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.
My question is, if I adjust the character encoding on Tomcat, will it serve
the MS character instead of a question mark?
Microsoft style apostrophe.
[wince]
> My question is, if I adjust the character encoding on Tomcat, will it serve
> the MS character instead of a question mark? I read the default encoding is
> ISO-8859-1, which I thought would include this mystery character, but
> apparently it do
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.
My question is, if I adjust the characte
On 18.06.2010 13:50, Felix Schumacher wrote:
On Fri, 18 Jun 2010 12:50:31 +0200, Rainer Jung
wrote:
On 18.06.2010 11:04, Felix Schumacher wrote:
On Thu, 17 Jun 2010 19:32:36 +0400, Konstantin Kolinko
wrote:
2010/6/17 Felix Schumacher:
apache httpd thinks it would be better to append a
char
On Fri, 18 Jun 2010 12:50:31 +0200, Rainer Jung
wrote:
> On 18.06.2010 11:04, Felix Schumacher wrote:
>> On Thu, 17 Jun 2010 19:32:36 +0400, Konstantin Kolinko
>> wrote:
>>> 2010/6/17 Felix Schumacher:
For the moment I have written a filter, which sets a default
encoding,
>> as
soon as
On 18.06.2010 11:04, Felix Schumacher wrote:
On Thu, 17 Jun 2010 19:32:36 +0400, Konstantin Kolinko
wrote:
2010/6/17 Felix Schumacher:
For the moment I have written a filter, which sets a default encoding,
as
soon as Response.setContentType(String type) is called and
type.startsWith("text/"
On Thu, 17 Jun 2010 19:32:36 +0400, Konstantin Kolinko
wrote:
> 2010/6/17 Felix Schumacher :
>> For the moment I have written a filter, which sets a default encoding,
as
>> soon as Response.setContentType(String type) is called and
>> type.startsWith("text/"). That works for the moment, but I woul
2010/6/17 Felix Schumacher :
> For the moment I have written a filter, which sets a default encoding, as
> soon as Response.setContentType(String type) is called and
> type.startsWith("text/"). That works for the moment, but I would prefer the
> solution described in above thread.
I know that sett
On 17/06/2010 15:23, Felix Schumacher wrote:
> My Question now is, should I file a bug to enhance DefaultServlet? If so
> would it be legal to include the patch from that discussion?
That is covered by section 5 of the ALv2, so yes it would be legal. Make
sure you correctly attribute it. I'd add t
Hi,
I have a character encoding problem with the DefaultServlet.
We use it to serve static html content, which is encoded in utf-8.
The DefaultServlet doesn't set characterset in the response, so the
browser looks for a meta-tag describing the encoding. Luckily these are set
in our conten
Thanks Chuck, problem fixed
Peter
From: Peter Sparkes [mailto:pe...@didm.co.uk]
Subject: Setting Character Encoding in server.xml
I am using Linux/Tomcat 5.5.
I am running several Tomcat instances each with its own server.xml and
wish to use different character encoding in each instance
> From: Peter Sparkes [mailto:pe...@didm.co.uk]
> Subject: Setting Character Encoding in server.xml
>
> I am using Linux/Tomcat 5.5.
>
> I am running several Tomcat instances each with its own server.xml and
> wish to use different character encoding in each instance.
>
Hi,
I am using Linux/Tomcat 5.5.
I am running several Tomcat instances each with its own server.xml and
wish to use different character encoding in each instance.
Please how do I set the character encoding in server.xml
Thanks
Peter
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
My company recently decided to alter our password complexity
requirements for our webapp, and I got to implement the changes. What fun!
We use a regular expression to enforce our password complexity, and it
needed to be changed. Since we are sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Halm,
On 10/8/2009 3:20 AM, Halm Reusser wrote:
> Christopher Schultz wrote:
>
>> Give [accept-charset] a try and see what happens.
>
> Does neither work. But thanks.
:(
Does the client send a Content-Type header including a charset if you
explici
Christopher Schultz wrote:
On that page is a POST form. When I evaluate the posted data, they are NOT
utf-8 encoded.
/Most/ clients will act the way you expect, yet, there is no requirement
for them to do so. What client is this, by the way?
Firefox 3.5.3, IE7, Safari 4.0.3
See the W3C doc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Halm,
On 10/7/2009 11:44 AM, Halm Reusser wrote:
> Peter Crowther wrote:
>> What are you trying to achieve? If we know more about the problem you're
>> trying to solve, we may be able to suggest some different approaches.
>
> The client receives an
Halm Reusser wrote:
> Hi Markus,
>
> thanks for your hints.
>
> Markus Meyer wrote:
>> It all depends on the client. IIRC if you set the charset in the
>> content type header to utf-8, like this
>>
>> contentType="text/html; charset=utf-8"
>>
>> most browsers will then use utf-8 for HTTP GET and
Hi Andre-John,
Andre-John Mas wrote:
I wan't do it within the application. I prefer to configure the app
container or the app itself.
I had asked for this too a while back, but I was told the RFC indicates
ISO-8859-1, so the developers didn't want to allow you to change the
default encoding
Hi Markus,
thanks for your hints.
Markus Meyer wrote:
It all depends on the client. IIRC if you set the charset in the content
type header to utf-8, like this
contentType="text/html; charset=utf-8"
most browsers will then use utf-8 for HTTP GET and POST requests when
responding to the given
Hi Peter,
Peter Crowther wrote:
What are you trying to achieve? If we know more about the problem you're
trying to solve, we may be able to suggest some different approaches.
The client receives an HTML page with contentType="text/html; charset=utf-8"
On that page is a POST form. When I eval
On 1-Oct-2009, at 07:22, Halm Reusser wrote:
Pid wrote:
How about?
request.setCharacterEncoding("ENCODING");
I wan't do it within the application. I prefer to configure the app
container or the app itself.
I had asked for this too a while back, but I was told the RFC
indicates ISO-8859
It all depends on the client. IIRC if you set the charset in the content
type header to utf-8, like this
contentType="text/html; charset=utf-8"
most browsers will then use utf-8 for HTTP GET and POST requests when
responding to the given page.
See this thread for some more information:
http
2009/10/1 Halm Reusser :
> Is there a possibility to force the client to use a specific encoding?
No. Consider the first request a client makes: it has to create and
send a HTTP request with no prior knowledge of, or communication with,
the server. So it has no way of asking the server what enco
Pid wrote:
How about?
request.setCharacterEncoding("ENCODING");
I wan't do it within the application. I prefer to configure the app container
or the app itself.
Bearing in mind that you're not really changing what the client
requests, or might expect you to be setting...
Is there a poss
On 01/10/2009 10:44, Halm Reusser wrote:
Hi,
Calling <%= request.getCharacterEncoding() %> in a jsp deployed in a
Tomcat 6.0.20 container returns null.
Is there any possibility to force a default CharacterEncoding for such
requests?
How about?
request.setCharacterEncoding("ENCODING");
Bear
Halm Reusser wrote:
Hi,
Calling <%= request.getCharacterEncoding() %> in a jsp deployed in a
Tomcat 6.0.20 container returns null.
Is there any possibility to force a default CharacterEncoding for such
requests?
Don't worry, there is already a default.
The only problem is to figure out wh
Hi,
Calling <%= request.getCharacterEncoding() %> in a jsp deployed in a Tomcat
6.0.20 container returns null.
Is there any possibility to force a default CharacterEncoding for such requests?
Thanks in advance!
Regards,
--
SWITCH
Serving Swiss Universities
--
Halm Re
> From: Zhou, Yan [mailto:[EMAIL PROTECTED]
> Subject: how to set character encoding in Tomcat 6.0
>
> response.setCharacterEncoding("UTF-7");
Java does not normally include UTF-7 support (probably a good thing). There is
a SourceForge package you might try if you really,
Hi There,
With the default Tomcat 6.0, the following results in
"UnsupportedEncodingException", how do I configure Tomcat for different
encoding?
I am setting the response in my Servlet:
response.setCharacterEncoding("UTF-7");
Thanks,
Yan Zhou
Confidentiality Notice
-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?
Chris, I finally found it.
My server.xml was not correctly configured. My fault.
Again, thank you all for your help.
- Original Message
From: Christopher Schultz <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Wednesday, June 18, 2008 11:12:45 PM
Subject: Re: Character en
-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 . Are you using more than one
| connector? Are you usin
-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
M does and so tomcat read them indirectly through it??
Cheers
- Original Message
From: Christopher Schultz <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Wednesday, June 18, 2008 9:42:21 PM
Subject: Re: Character encoding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nch,
Chris, thanks for your help.
Please, see my comments bellow.
Kind regards.
- Original Message
From: Christopher Schultz <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Wednesday, June 18, 2008 9:42:21 PM
Subject: Re: Character encoding
-BEGIN PGP SIGNED MESSAGE-
Hash
-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 yo
e environment dependent?
Hope this is useful. Lots of thanks to you all.
- Original Message
From: Christopher Schultz <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Wednesday, June 18, 2008 7:25:03 PM
Subject: Re: Character encoding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-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 o
-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
- Original Message -
From: "Johnny Kewl" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Wednesday, June 18, 2008 6:26 PM
Subject: Re: Character encoding
- Original Message -
From: "nch" <[EMAIL PROTECTED]>
To: "Tomcat U
- Original Message -
From: "nch" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
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
s
- 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 an
gt;
To: Tomcat Users List
Sent: Wednesday, June 18, 2008 4:29:54 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
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
'm having this problem in debian etch (works fine in windows xp).
Many thanks.
- Original Message
From: Christopher Schultz <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Wednesday, June 18, 2008 3:56:13 PM
Subject: Re: Character encoding
-BEGIN PGP SIGNED MESSAGE-
Hash:
-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
t
Hi, there.
I'm having difficulties trying to decode URI parameters into UTF8.
I tried setting URIEncoding="UTF-8" and useBodyEncodingForURI="true" Connector
properties. Didn't work.
I tried adding a Filter by following the example at
http://tompson.wordpress.com/2007/01/29/encoding-filter-for-ja
verride the encoding used to send the
data:
The HTML 4 specification says this about the accept-charset attribute:
"The default value for this attribute is the reserved string "UNKNOWN".
User agents may interpret this value as the character encoding that was
used to transmit the d
HTTP header (and can be overridden by using
> request.setCharacterEncoding). Some broken clients don't provide the
> character encoding of the request, which makes things difficult sometimes.
What determines what's specified in the HTTP header for the value of the
encoding? Is it pur
e 's URIEncoding parameter. 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 of the request, which makes thin
ding of cookies for both incoming requests and outgoing
responses?
Thanks.
--
View this message in context:
http://www.nabble.com/Character-encoding-tf4031134.html#a11450938
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
Mester József wrote:
> 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 have
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
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
SetCharacterEncoding filter config into the global web.xml,
and delete the SetCharacterEncoding filter config from each web application,
it works ok, thanks again !
Caldarale, Charles R wrote:
>
>> From: lovetide [mailto:[EMAIL PROTECTED]
>> Subject: Feature request: Server level cha
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
lovetide wrote:
> 2. We afraid the efficiency of character encoding conversion: The data
> POSTed from FORM are already x-www-form-urlencoded, if these data can be
> converted directly into UTF-8 instead of internal character encoding of
> Tomcat (is it iso-8859-1 ?), then it may be mo
Mester József 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) there must be a switch
> added to the c
> From: lovetide [mailto:[EMAIL PROTECTED]
> Subject: Feature request: Server level character encoding
> instead adding afilter for each web application.
>
> 1. Repeated configuration is too bored: If Tomcat supplied
> that feature, we can delete the same config from each
We have many web applications running on Tomcat, and we choose UTF-8
character encoding for each web application, so we must add a
SetCharacterEncoding filter for each web application to make sure the data
POSTed from a FORM can be processed correctly.
As I know, Tomcat has a server.xml config
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) ca
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) there must be a switch added
to the call to java.exe. The
switch is:
-Dfile.encoding=UTF-8
But
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
dizzi wrote:
> Im not sure if this is problem of tomcat, but i think that its most
> probable.
Unlikely. I haven't seen a valid bug in this area for quite some time.
It is usually a combination of configuration (check the URIEncoding
property of your connector) and application errors. For a correc
Im not sure if this is problem of tomcat, but i think that its most
probable.
Problem:
Data received from form are not encoded corectly. (tomcat 5.5, utf-8, win
xp/RHEL4, struts)
Symptoms:
Data in request are completly screwed. (no matter if im displaying it in
utf-8 console, or sending b
I have a tomcat 5.5 server running utf-8. For this I included
URIEncoding="UTF-8" in the server.xml for port80 in order fo r the browser
to be able to access files with embedded swedish characters in the .
How to run an older application that needs iso8859-1? Any directive in the
web.xml or some
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
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
1 - 100 of 115 matches
Mail list logo
