Re: Tomcat 8.5.19 corrupts static text files encoded with UTF-8

encoding-tc9-v1.patch >> >> Tomcat 8.5.x >> http://home.apache.org/~markt/patches/2017-07-30-default-servlet- >> encoding-tc85-v1.patch > > Thank you very much for your fast feedback. I applied the patch for Tomcat > 8.5.x and it seems to fix the issue: Static t

RE: Tomcat 8.5.19 corrupts static text files encoded with UTF-8

hank you very much for your fast feedback. I applied the patch for Tomcat 8.5.x and it seems to fix the issue: Static text/JavaScript files are served untouched (their encoding is not changed), which means JavaScript files encoded as UTF-8 (without BOM) are working again in the browser. Thanks!

Re: Tomcat 8.5.19 corrupts static text files encoded with UTF-8

On 30/07/17 10:50, Mark Thomas wrote: > On 30/07/17 10:21, Rémy Maucherat wrote: >> On Sun, Jul 30, 2017 at 10:59 AM, Konstantin Preißer >> wrote: >>> I honestly don't understand that change. As a web developer, I expect a >>> web server to serve static files exactly

Re: Tomcat 8.5.19 corrupts static text files encoded with UTF-8

ay, July 29, 2017 2:56 PM >>> >>>> (...) >>>> >>>> Why would Tomcat want to modify static files, instead of just serving >>>> them as-is? >>> >>> Because Tomcat now checks the response encoding and the file encoding &

Re: Tomcat 8.5.19 corrupts static text files encoded with UTF-8

> >Why would Tomcat want to modify static files, instead of just serving > > >them as-is? > > > > Because Tomcat now checks the response encoding and the file encoding > > and converts if necessary. > > > > You probably want to set the fileEncoding ini

RE: Tomcat 8.5.19 corrupts static text files encoded with UTF-8

checks the response encoding and the file encoding > and converts if necessary. > > You probably want to set the fileEncoding init param of the Default servlet to > UTF-8. Thanks. So I set the following parameter in web.xml: fileEncoding utf-8 T

Re: Tomcat 8.5.19 corrupts static text files encoded with UTF-8

On 28 July 2017 21:53:27 BST, "Konstantin Preißer" <kpreis...@apache.org> wrote: >Hi all, > >after quite a while I'm reporting back here, because I faced a problem >after updating to Tomcat 8.5.19: Suddenly, static text files (.txt, .js >etc.) encoded with UTF-8 (wit

Tomcat 8.5.19 corrupts static text files encoded with UTF-8

Hi all, after quite a while I'm reporting back here, because I faced a problem after updating to Tomcat 8.5.19: Suddenly, static text files (.txt, .js etc.) encoded with UTF-8 (without BOM) are getting corrupted when they are served to the browser. This didn't happen with Tomcat 8.5.16

Re: does Tomcat 8.5.9 have UTF-8 encoding throughout by default?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 To whom it may concern, On 1/7/17 5:57 PM, modjkl...@comcast.net wrote: > Anyone know if it has UTF-8 encoding throughout out-of-the-box, or > do I need to configure it to be so? > > I'm seeing some headers using iso-8859-1 and I'm no

Re: does Tomcat 8.5.9 have UTF-8 encoding throughout by default?

On 07.01.2017 23:57, modjkl...@comcast.net wrote: Anyone know if it has UTF-8 encoding throughout out-of-the-box, or do I need to configure it to be so? I'm seeing some headers using iso-8859-1 and I'm not sure where they're being generated. Hi. You are not being very explicit as to what

does Tomcat 8.5.9 have UTF-8 encoding throughout by default?

Anyone know if it has UTF-8 encoding throughout out-of-the-box, or do I need to configure it to be so? I'm seeing some headers using iso-8859-1 and I'm not sure where they're being generated.

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

in the HTTP protocol. And the people in charge of the design of the protocol missed a golden opportunity of cleaning this up in HTTP 2.x and making Unicode/UTF-8 the default, instead of clinging to iso-8859-1. Thus condemning all web programmers worldwide to another 20 years of obscure bugs and clunky work-

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

; Unfortunately, this is is still a big mess in the HTTP protocol. > And the people in charge of the design of the protocol missed a golden > opportunity of cleaning this up in HTTP 2.x and making Unicode/UTF-8 the > default, instead of clinging to iso-8859-1. Thus condemning all web >

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

hunk.getCharset() is called from MessageBytes.toBytes() which is called from AjpMessage.appendBytes(MessageBytes) So, I think this explains why my data is being interpreted incorrectly. Now, the question becomes why isn't this line in server.xml: enough to cause ByteChunk.charset to be set to "UTF-8"

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

EFAULT_CHARSET; } return charset; } I set a breakpoint on ByteChunk.setCharset(Charset) and it is never executed. ByteChunk.getCharset() is called from MessageBytes.toBytes() which is called from AjpMessage.appendBytes(MessageBytes) So, I think this explains why my data i

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

the above characters/bytes sequences look quite like a double UTF-8 encoding took place : - an "Ë", would be encoded in UTF-8 as the 2 bytes 0xc3 0x8b (which seen as ISO-8859-1 bytes/characters, would look like "A tilde" followed by an unprintable control character) - then if yo

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Oct 18, 2016 6:22 PM, "Mark Thomas" wrote: > > I wonder if it is worth a clean install of httpd, mod_jk and Tomcat and > then running a simple test. > > Mark > That would be difficult to justify without more evidence than ive got. Do you know if apache has a test suite I

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On 18/10/2016 23:10, Mark Juszczec wrote: > On Oct 18, 2016 5:37 PM, "Mark Thomas" wrote: >> >> >> Java handles bytes as signed (-128 to 127) but the data in the input >> stream is unsigned. The additional Fs are an artefact of whatever those >> bytes were cast to. >> >> It

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Oct 18, 2016 5:37 PM, "Mark Thomas" wrote: > > > Java handles bytes as signed (-128 to 127) but the data in the input > stream is unsigned. The additional Fs are an artefact of whatever those > bytes were cast to. > > It looks normal to me. That's what i thought but didn't

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On 18/10/2016 22:29, Mark Juszczec wrote: > On Oct 18, 2016 4:45 PM, "Mark Juszczec" wrote: >> >> >> >> On Tue, Oct 18, 2016 at 2:58 PM, Mark Juszczec > wrote: >> >> Converting them to hex I see >> >> -61 = FFC3 >> >> -117 =

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Oct 18, 2016 4:45 PM, "Mark Juszczec" wrote: > > > > On Tue, Oct 18, 2016 at 2:58 PM, Mark Juszczec wrote: > > Converting them to hex I see > > -61 = FFC3 > > -117 = FF8B > > I know > > Ë = 0xC3 0x8B > > so I'm assuming

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Tue, Oct 18, 2016 at 2:58 PM, Mark Juszczec wrote: > > > Some questions (if these are not relevant, please disregard): > > I'm loading a whole bunch of modules. Could some of them be incompatible? > > DocumentRoot refers to a directory that does not exist. Is that a

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

zh-CN .zh-cn AddLanguage zh-TW .zh-tw LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW ForceLanguagePriority Prefer Fallback TypesConfig /etc/mime.types DefaultType None AddType application/x-compress .Z AddType application/x-

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Tue, Oct 18, 2016 at 10:23 AM, André Warnier (tomcat) wrote: > > > Good. That our goal here. We live to help :-) > > You all have been helpful beyond description. > I don't think that there is a need for a formal "petition". This being a > Tomcat list, and the mod_jk

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On 18.10.2016 16:16, Mark Juszczec wrote: On Tue, Oct 18, 2016 at 10:10 AM, André Warnier (tomcat) wrote: This being a list dedicated to Tomcat, maybe we are going a bit deep in the Apache httpd configuration and precedence rules here. It is anyway difficult to answer your

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Tue, Oct 18, 2016 at 10:10 AM, André Warnier (tomcat) wrote: > > This being a list dedicated to Tomcat, maybe we are going a bit deep in > the Apache httpd configuration and precedence rules here. > It is anyway difficult to answer your questions, without seeing the whole >

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On 18.10.2016 15:22, Mark Juszczec wrote: On Tue, Oct 18, 2016 at 9:13 AM, Mark Juszczec wrote: DocumentRoot /some/dir/thatDoesNotExist/ JkEnvVar nameWithIntlChar JkMount /myService/* lbAjpWorker JkMount /myService lbAjpWorker I

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Tue, Oct 18, 2016 at 9:13 AM, Mark Juszczec wrote: > > > > DocumentRoot /some/dir/thatDoesNotExist/ > JkEnvVar nameWithIntlChar > JkMount /myService/* lbAjpWorker > JkMount /myService lbAjpWorker > > > > I forgot to ask something. The above

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Tue, Oct 18, 2016 at 8:36 AM, André Warnier (tomcat) wrote: > On 18.10.2016 13:03, Mark Juszczec wrote: >> >> >> No, the following line: >> >> JkOptions +ForwardKeySize +ForwardURIEscaped -ForwardDirectories >> >> is in an Apache conf file, but not in a VirtualHost entry. >>

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On 18.10.2016 13:03, Mark Juszczec wrote: On Tue, Oct 18, 2016 at 1:14 AM, Rainer Jung wrote: Am 17.10.2016 um 22:38 schrieb Mark Juszczec: I've tried adding +ForwardURIEscaped in my conf file as follows: # JkOptions indicate to send SSL KEY SIZE, JkOptions

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Tue, Oct 18, 2016 at 1:14 AM, Rainer Jung wrote: > Am 17.10.2016 um 22:38 schrieb Mark Juszczec: > >> >> >> I've tried adding +ForwardURIEscaped in my conf file as follows: >> >> # JkOptions indicate to send SSL KEY SIZE, >> JkOptions +ForwardKeySize

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

Am 17.10.2016 um 22:38 schrieb Mark Juszczec: On Mon, Oct 17, 2016 at 8:20 AM, Rainer Jung wrote: Am 17.10.2016 um 12:35 schrieb Mark Juszczec: On Mon, Oct 17, 2016 at 4:29 AM, Mark Thomas wrote: A small hint. I'd expect those to be % encoded.

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

On Mon, Oct 17, 2016 at 8:20 AM, Rainer Jung wrote: > Am 17.10.2016 um 12:35 schrieb Mark Juszczec: > >> On Mon, Oct 17, 2016 at 4:29 AM, Mark Thomas wrote: >> >> >>> A small hint. I'd expect those to be % encoded. >>> >>> >> Thank you very much for

Re: Is UTF-8 used everywhere for Tomcat 8.5.6?

/2016-10-17 19:59 GMT+03:00 R <bittransfer2...@gmail.com>: > Hi, > > I have a default installation of Tomcat 8.5.6. When I make a POST request > with a tilde character, and the encoding is set to UTF-8, it seems that my > servlet handler is decoding it incorrectly. I have

Re: Is UTF-8 used everywhere for Tomcat 8.5.6?

On 17/10/2016 17:59, R wrote: > Hi, > > I have a default installation of Tomcat 8.5.6. When I make a POST request > with a tilde character, and the encoding is set to UTF-8, it seems that my > servlet handler is decoding it incorrectly. The tilde character should not need to be en

Is UTF-8 used everywhere for Tomcat 8.5.6?

Hi, I have a default installation of Tomcat 8.5.6. When I make a POST request with a tilde character, and the encoding is set to UTF-8, it seems that my servlet handler is decoding it incorrectly. I have to set the character encoding on the HttpServletRequest parameter to decode properly, example

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

Is that correct? That is the correct UTF-8 byte encoding for the characters AOËL. A small hint. I'd expect those to be % encoded. Thank you very much for your reply. I've been thinking the problem is lack of % encoding after reading: *"Default encoding for GET* The character set for HTTP query strings

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

>> pos=4 len=1411 max=8192" (at > >> ajp_connection_tcp_send_message::jk_ajp_common.c) shows them to be: > >> > >> 41 4f c3 8b 4c > >> > >> AFAIK this means the correct bytes are being sent to AJP. Is that > correct? > > > > That

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

th the message >> >> "ajp_connection_tcp_send_message::jk_ajp_common.c (1208): sending to ajp13 >> pos=4 len=1411 max=8192" (at >> ajp_connection_tcp_send_message::jk_ajp_common.c) shows them to be: >> >> 41 4f c3 8b 4c >> >> AFAIK this means th

Re: Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

.c (1208): sending to ajp13 > pos=4 len=1411 max=8192" (at > ajp_connection_tcp_send_message::jk_ajp_common.c) shows them to be: > > 41 4f c3 8b 4c > > AFAIK this means the correct bytes are being sent to AJP. Is that correct? That is the correct UTF-8 byte encoding for the characters AO

Tomcat 8, AJP 1.3 UTF-8/ISO-8859-1 conversion problem

er.process() is invoked I have UTF-8 specified as URIEncoding in ajp and it has had no effect. Ive also specified useBodyEncodingForURI as true with no effect. Conventional wisdom says the data is getting inadvertently as ISO-8859-1 somewhere along the line. Since the data is correct (per mod_jk.lo

Re: How to set tomcat 8.0.20 container character encoding of request and response to UTF-8 intead of ISO-8859-1

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.apache.org/tomcat/FAQ/CharacterEncod

Re: How to set tomcat 8.0.20 container character encoding of request and response to UTF-8 intead of ISO-8859-1

*Thanks and RegardsAkshat Tandon* On Tue, Feb 16, 2016 at 8:13 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > 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

Re: How to set tomcat 8.0.20 container character encoding of request and response to UTF-8 intead of ISO-8859-1

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.

How to set tomcat 8.0.20 container character encoding of request and response to UTF-8 intead of ISO-8859-1

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

Re: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

On 1/25/2015 4:29 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 1/24/15 7:52 AM, André Warnier wrote: Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, ... Morality : in web applications, always specify the

Re: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 1/24/15 7:52 AM, André Warnier wrote: Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, ... Morality : in web applications, always specify the content-type (and character set, if applicable)

Re: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

Caldarale, Charles R wrote: From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header German has its own confusing quirks. I always liked Schmetterling; the sound is so counter-indicative

RE: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header German has its own confusing quirks. I always liked Schmetterling; the sound is so counter-indicative of the actual entity

Re: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

Martin Knoblauch wrote: On Sat, Jan 24, 2015 at 1:52 PM, André Warnier a...@ice-sa.com wrote: Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, ... Morality : in web applications, always specify the content-type (and character set, if applicable) of

Re: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, ... Morality : in web applications, always specify the content-type (and character set, if applicable) of what you are returning. To André: the word you are looking for is Moral, not Morality. A moral is

Re: [OT] Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

On Sat, Jan 24, 2015 at 1:52 PM, André Warnier a...@ice-sa.com wrote: Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, ... Morality : in web applications, always specify the content-type (and character set, if applicable) of what you are returning.

Re: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 1/23/15 5:04 AM, André Warnier wrote: It was actually a good question, and a good explanation of your problem. Bonus points for that. That you found the solution yourself afterward, and communicated this to the list, are two

Re: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 David, On 1/23/15 8:26 AM, David kerber wrote: On 1/23/2015 5:04 AM, André Warnier wrote: A part of what I wanted to say in my original answer, is that just by taking the time to actually think about the problem you are having, and writing down

[OT] Re: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

On 23/01/2015 21:16, Christopher Schultz wrote: David, On 1/23/15 8:26 AM, David kerber wrote: On 1/23/2015 5:04 AM, André Warnier wrote: A part of what I wanted to say in my original answer, is that just by taking the time to actually think about the problem you are having, and writing

RE: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

of the things I found is that few of the jsp pages itself was encoded differently and not utf-8 and once I fixed that it do not completely worked. After lots of trial and error, Two settings which worked for me are by adding contenttype tag in jsp page %@ page contentType=text/html; charset=UTF-8

Re: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

to get the minimal setting which would help, some of the things I found is that few of the jsp pages itself was encoded differently and not utf-8 and once I fixed that it do not completely worked. After lots of trial and error, Two settings which worked for me are by adding contenttype tag

Re: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

On 1/23/2015 5:04 AM, André Warnier wrote: A part of what I wanted to say in my original answer, is that just by taking the time to actually think about the problem you are having, and writing down a clear explanation for someone else, you often find the solution yourself. Add in the exercise

Re: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

Subject: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header Hi all, Firs off Sorry if this question appears too noob. Currently in my application I get this warning. HTML1114: Codepage iso-8859-1 from (HTTP header) overrides conflicting codepage

RE: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

@tomcat.apache.org Subject: Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header Hi all, Firs off Sorry if this question appears too noob. Currently in my application I get this warning. HTML1114: Codepage iso-8859-1 from (HTTP header) overrides

Tomcat 8 encoding issues: unable to change the default encoding iso-8859-1 to utf-8 in http header

Hi all, Firs off Sorry if this question appears too noob. Currently in my application I get this warning. HTML1114: Codepage iso-8859-1 from (HTTP header) overrides conflicting codepage utf-8 from (META tag) File: index.action Application uses struts 2, spring, hibernate, jpa + tiles 3

UTF-8 encoded request URI

Hi I am getting bad request from tomcat when I send UTF-8 encoded request to my application. I have configured connector in my server.xml with URIEncoding=”UTF-8”. I have set charset in the request to UTF-8. How can I solve 400 Bad request? How can I tell tomcat to decode request URI instead

Re: UTF-8 encoded request URI

Lulseged Zerfu wrote: Hi I am getting bad request from tomcat when I send UTF-8 encoded request to my application. I have configured connector in my server.xml with URIEncoding=”UTF-8”. I have set charset in the request to UTF-8. How can I solve 400 Bad request? How can I tell tomcat

Re: UTF-8 encoded request URI

On Wed, Sep 3, 2014 at 7:45 AM, Lulseged Zerfu zlulse...@hotmail.com wrote: Hi I am getting bad request from tomcat when I send UTF-8 encoded request to my application. Can you give an example of the request? Are the non-ascii characters in the URL or in the payload of your request (or both

Re: UTF-8 encoded request URI

On 03/09/2014 12:45, Lulseged Zerfu wrote: Hi I am getting bad request from tomcat when I send UTF-8 encoded request to my application. I have configured connector in my server.xml with URIEncoding=”UTF-8”. I have set charset in the request to UTF-8. How can I solve 400 Bad request? Don't

Re: UTF-8 encoded request URI

On 9/3/2014 4:52 AM, Mark Thomas wrote: On 03/09/2014 12:45, Lulseged Zerfu wrote: Hi I am getting bad request from tomcat when I send UTF-8 encoded request to my application. I have configured connector in my server.xml with URIEncoding=”UTF-8”. I have set charset in the request to UTF-8

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

Greetings, On Wed, Jun 26, 2013 at 4:08 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, But, even when sending UTF-8 encoded data according to this principle, they are *not* indicating that it is UTF-8 data, which

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

Shanti Suresh wrote: Greetings, On Wed, Jun 26, 2013 at 4:08 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, But, even when sending UTF-8 encoded data according to this principle, they are *not* indicating

Re: FORM based authentication and utf-8 encoding of credentials

is not sending that correctly. The password is UTF-8 encoded but the Content-Type fails to specify the character set used. It it did, Tomcat would treat the password as UTF-8. This is a common failing of browsers and is covered in the FAQ. [1] Well I have tried IE, Firefox, Chrome. None of them is appending

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

The browser is not sending that correctly. The password is UTF-8 encoded but the Content-Type fails to specify the character set used. It it did, Tomcat would treat the password as UTF-8. This is a common failing of browsers and is covered in the FAQ. [1] Well I have tried IE, Firefox, Chrome. None

Re: FORM based authentication and utf-8 encoding of credentials

-www-form-urlencoded j_username=pj_password=%C5%BDe%C5%BEUli%C4%8Dka.1 The browser is not sending that correctly. The password is UTF-8 encoded but the Content-Type fails to specify the character set used. It it did, Tomcat would treat the password as UTF-8. This is a common failing

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

Content-Type: application/x-www-form-urlencoded j_username=pj_password=%C5%BDe%C5%BEUli%C4%8Dka.1 The browser is not sending that correctly. The password is UTF-8 encoded but the Content-Type fails to specify the character set used. It it did, Tomcat would treat the password as UTF-8

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

this with HTML is: meta http-equiv=Content-Type content=text/html; charset=utf-8 Firefox reads the body in UTF-8 then, which is fine, but the charset used in forms is still ISO-8859-1, so you have to add accept-charset=utf-8 to the form just for firefox (other browser automatically use UTF-8

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

the common way to override this with HTML is: meta http-equiv=Content-Type content=text/html; charset=utf-8 Firefox reads the body in UTF-8 then, which is fine, but the charset used in forms is still ISO-8859-1, so you have to add accept-charset=utf-8 to the form just for firefox (other browser

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

is encoded in ISO-8859-1 the common way to override this with HTML is: meta http-equiv=Content-Type content=text/html; charset=utf-8 (...) --- That person is plainly wrong. You must not use different values in Content-Type HTTP header and in Content-Type META tag. 1. The HTML spec

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

... And this is a real bug: If the HTTP header says the file is encoded in ISO-8859-1 the common way to override this with HTML is: meta http-equiv=Content-Type content=text/html; charset=utf-8 Firefox reads the body in UTF-8 then, which is fine, but the charset used in forms is still ISO-8859

Re: [slightly OT] FORM based authentication and utf-8 encoding of credentials

since 8 years... And this is a real bug: If the HTTP header says the file is encoded in ISO-8859-1 the common way to override this with HTML is: meta http-equiv=Content-Type content=text/html; charset=utf-8 Firefox reads the body in UTF-8 then, which is fine, but the charset used

FORM based authentication and utf-8 encoding of credentials

/myapp/j_security_check HTTP/1.1 Content-Type: application/x-www-form-urlencoded j_username=pj_password=%C5%BDe%C5%BEUli%C4%8Dka.1 The first letter Ž is really encoded in the utf-8 as bytes in hexa C5, BD. But in the method public Principal authenticate(String username, String credentials

RE:FORM based authentication and utf-8 encoding of credentials

Where do you store your login/password : DB ? xml file ? encrypted in xml file ? De : Jan Vávra [va...@602.cz] Envoyé : lundi 24 juin 2013 13:36 À : Tomcat Users List Objet : FORM based authentication and utf-8 encoding of credentials Hello, I'm

Re: FORM based authentication and utf-8 encoding of credentials

length is 14. And that corresponds to the fact that in credentials is stored some form of utf-8 encoding. Utf-8 encoding string ŽežUlička.1 has length 14. +1 for each letter: Ž,ž,č. Jan. Where do you store your login/password : DB ? xml file ? encrypted in xml file

Re: FORM based authentication and utf-8 encoding of credentials

Content-Type: application/x-www-form-urlencoded j_username=pj_password=%C5%BDe%C5%BEUli%C4%8Dka.1 The browser is not sending that correctly. The password is UTF-8 encoded but the Content-Type fails to specify the character set used. It it did, Tomcat would treat the password as UTF-8

Re: another UTF-8 problem

Thanks for your responses. The problem was not the response from the web service. Something must have been completely mixed up. I set the Java option -Dfile.encoding to utf-8 which solved the write to file problem and also put this in the code: if (req.getCharacterEncoding() == null

another UTF-8 problem

Hi, I've encountered a UTF-8 problem and yes, URIEncoding=UTF-8 is set. I'm connecting to a web service which returns UTF-8 encoded data. If I do so from a plain, regular, self-contained Java application everything is fine. However, if I run the same classes in tomcat (and trigger the action

RE: another UTF-8 problem

From: Tim-Christian Mundt [mailto:d...@tim-erwin.de] Subject: another UTF-8 problem I've encountered a UTF-8 problem and yes, URIEncoding=UTF-8 is set. Tomcat version? Using APR or not? JVM version? Platform? Default locale setting? - Chuck THIS COMMUNICATION MAY CONTAIN

Re: another UTF-8 problem

Caldarale, Charles R schrieb: From: Tim-Christian Mundt [mailto:d...@tim-erwin.de] Subject: another UTF-8 problem I've encountered a UTF-8 problem and yes, URIEncoding=UTF-8 is set. Tomcat version? Using APR or not? JVM version? Platform? Default locale setting? - Chuck

Re: another UTF-8 problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim, On 8/24/2010 9:06 AM, Tim-Christian Mundt wrote: I've encountered a UTF-8 problem and yes, URIEncoding=UTF-8 is set. If you're connecting-out to a SOAP service, then the URIEncoding setting doesn't matter. I'm connecting to a web service

Re: UTF-8 encoding in Tomcat 6.0 fixed

- Original Message - From: André Warnier a...@ice-sa.com To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, August 03, 2010 5:30 PM Subject: Re: UTF-8 encoding in Tomcat 6.0 fixed michel wrote: - Original Message - From: michel compu...@videotron.ca To: Tomcat

Re: UTF-8 encoding in Tomcat 6.0

the filter, they will be mangled as ISO-8859-1. If this is different from previous behaviour, maybe I should report a bug. It works perfectly well for me when using URIEncoding=UTF-8. The Content-Type of the request is never consulted for any reason in this case, so its presence should not change

Re: UTF-8 encoding in Tomcat 6.0

and Regards Arun --- On Sun, 8/1/10, Mark Thomas ma...@apache.org wrote: From: Mark Thomas ma...@apache.org Subject: Re: UTF-8 encoding in Tomcat 6.0 To: Tomcat Users List users@tomcat.apache.org Date: Sunday, August 1, 2010, 5:05 AM On 31/07/2010 17:34, arun kumar wrote: I ran my example

Re: UTF-8 encoding in Tomcat 6.0

On 03/08/2010 12:18, arun kumar wrote: Am i sending some parameter wrongly? Probably. Go back and read what I wrote about the test JSP on the wiki and see if that works. Mark - To unsubscribe, e-mail:

Re: UTF-8 encoding in Tomcat 6.0

To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, August 03, 2010 7:25 AM Subject: Re: UTF-8 encoding in Tomcat 6.0 On 03/08/2010 12:18, arun kumar wrote: Am i sending some parameter wrongly? Probably. Go back and read what I wrote about the test JSP on the wiki and see

RE: UTF-8 encoding in Tomcat 6.0

works in Tomcat 6.0.20 http://localhost:8007/sampleweb/params?test=%D8 log output Servlet init IN doFilterUTF-8 Ø U+00D8 Ø c3 98 LATIN CAPITAL LETTER O WITH STROKE http://www.utf8-chartable.de/unicode-utf8-table.pl ? Martin __ do not alter

Re: UTF-8 encoding in Tomcat 6.0

?mydata=%d8 again ? is displayed Thanks and regards Arun --- On Tue, 8/3/10, Mark Thomas ma...@apache.org wrote: From: Mark Thomas ma...@apache.org Subject: Re: UTF-8 encoding in Tomcat 6.0 To: Tomcat Users List users@tomcat.apache.org Date: Tuesday, August 3, 2010, 7:25 AM On 03/08/2010 12:18

Re: UTF-8 encoding in Tomcat 6.0

...@apache.org wrote: From: Mark Thomas ma...@apache.org Subject: Re: UTF-8 encoding in Tomcat 6.0 To: Tomcat Users List users@tomcat.apache.org Date: Tuesday, August 3, 2010, 7:25 AM On 03/08/2010 12:18, arun kumar wrote: Am i sending some parameter wrongly? Probably. Go back and read what I

Re: UTF-8 encoding in Tomcat 6.0

- Original Message - From: michel compu...@videotron.ca To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, August 03, 2010 9:35 AM Subject: Re: UTF-8 encoding in Tomcat 6.0 I am having a simmilar problem with Tomcat Version 6.0.26. I have a JSP with some french characters

Re: UTF-8 encoding in Tomcat 6.0 fixed

- Original Message - From: michel compu...@videotron.ca To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, August 03, 2010 1:08 PM Subject: Re: UTF-8 encoding in Tomcat 6.0 - Original Message - From: michel compu...@videotron.ca To: Tomcat Users List users

Re: UTF-8 encoding in Tomcat 6.0 fixed

michel wrote: - Original Message - From: michel compu...@videotron.ca To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, August 03, 2010 1:08 PM Subject: Re: UTF-8 encoding in Tomcat 6.0 - Original Message - From: michel compu...@videotron.ca To: Tomcat Users List

Re: UTF-8 encoding in Tomcat 6.0

not behave the way you describe. A clean Tomcat install with no other components (reverse proxy etc) using the test encoding JSP from the wiki [1] works correctly with POST and GET (if URIEncoding=UTF-8 is used). Sorry Mark - i did not get what you said. Could you please elaborate? Decoding is happening

Re: UTF-8 encoding in Tomcat 6.0

Hi Erik Thanks very much for your responses. I can assure that i'm interested in this topic even now :). My scenario is this: 1. I use a web application that runs in JBOSS. 2. JBOSS uses a tomcat web container from what i can see. 3. To my application if i pass a UTF-8 encoded value in hex

Re: UTF-8 encoding in Tomcat 6.0

application if i pass a UTF-8 encoded value in hex e.g: http://server:port/servlet/param=%xx... Then %xx is not decoded properly. I initially used to send the request with a mozilla browser but later started sending it with a java program as well with the same results. I tried setting

  1   2   3   >