tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Elli Albek <e...@sustainlane.com>
Subject Re: Char Encoding text streams on Tomcat 5.5 and Linux
Date Thu, 03 Dec 2009 01:56:14 GMT
I was not replying to any post by you. I was replying to a post by a fellow
named Dan.

He states "I have been successful using the charset filters on HTTP posts
and  XML"

I am not sure I can respond to your comments since it seems that we talk
about different topics. In either case, why vent?

E

On Wed, Dec 2, 2009 at 8:17 AM, Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Elli,
>
> On 12/2/2009 2:40 AM, Elli Albek wrote:
> > On your Linux box type “locale” + enter. The results should be UTF 8. If
> not
> > change it.
>
> I can have my locale set to whatever I'd like, thank you very much.
>
> > You can also set it in the file encoding java environment
> > variable as suggested above as extra safety measure.
>
> Well, you can check it's value. By default, it's UTF-8 on my system (as
> mentioned in my post if you read the whole thing).
>
> > Tomcat’s logic of determining the encoding from the request only applies
> > when Tomcat is parsing text in the request.
>
> Tomcat's logic of determining the encoding for the request is mandated
> by the servlet spec and the HTTP spec. In this case, Tomcat /was/
> parsing text in the request: we are talking about POST data, here. Elli,
> please read the posts before replying.
>
> > However if you read from the stream directly, using
> request.getInputStream()
> > you are getting binary data. When you create java.io.Reader from that
> input
> > stream you need to specify the encoding, or it will default to the file
> > system encoding.
>
> Yes. If you look at the source code to Tomcat, you'll see that the
> encoding used comes from the request headers, or defaults to ISO-8859-1.
> I'm not going to repeat this again.
>
> If you create your own Reader (which you shouldn't be doing), you're on
> your own. In this case, nobody was creating their own Reader.
>
> > The fact that tomcat is using ISO-8859-1 to read characters is not
> relevant
> > if you are reading from the stream directly and use your own Reader to
> > convert to characters.
>
> ..which I wasn't doing. Rather than repeatedly complaining about how you
> haven't read this thread properly, I'm simply going to stop.
>
> > I am assuming this is a likely cause, since the XML
> > parsing succeeds
>
> Okay, I can't help myself: when did we start talking about XML?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAksWkwEACgkQ9CaO5/Lv0PCI1QCgkC9SPmdWkHDPiLmEqE9l3xGm
> ASIAoLViW6EMWL67yVxBfMEJDXj9utR4
> =R438
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message