On Mon, 27 Oct 2008 08:36:03 -0500 "Caldarale, Charles R" <[EMAIL PROTECTED]> wrote:
> > From: Maxim Kuleshov [mailto:[EMAIL PROTECTED] > > Subject: encoding in URI after form-based redirect > > > > Question refers to 5.5 branch (5.5.25 from ubuntu repos). > > If possible, try the problem URI with the latest 5.5 version from the > Tomcat web site. > > > I use useBodyEncodingForURI=true mode in connector. > > All content is UTF-8 encoded. > > How could I fix of bypass such behaviour? > > Have you read the FAQ? > http://wiki.apache.org/tomcat/FAQ/CharacterEncoding > Thanks. I read about characterEncoding issue couple of years ago, when had upgraded to 5.5 branch. > Since everything should be UTF-8, have your tried setting the > URIEncoding attribute to that in your <Connector> elements? (You may > want to remove the useBodyEncodingForURI when you do so.) The problem is - not everything. There is at least one legacy application written for cp1251. I treat the problem as a bug, because exactly the same request produces two different results, dependent on where page was redirected from - form-based authenticator or anything else. If setCharacterEncoding doesn't work by reason of FormAuthenticator already accessed request content, when how I could intercept it? I've already tried custom FormAuthenticator valve config (characterEncoding field, but it seems it only affects login and password parameters). --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
