It's a good day for encoding problems. > For example: > > I traced the urlencoded POST data of an Über (%C3%9Cber) found it has proper > POST escape encoding (Unicode UTF-8: U+00DC (Ü) C39C LATIN CAPITAL LETTER > U WITH DIAERESIS) > > When Jbossweb interprets the posted urlencoded data w/CAS filters, hex.C3 is > interpreted as ASCII 195 (Ã) and hex.9C as ASCII 156 (œ) which is how the > Über is recorded (incorrectly) in the database and later displayed > (incorrectly).
Have you configured CAS for end-end UTF-8 support as described in https://wiki.jasig.org/display/CASUM/Internationalization? Let us know the result in that case. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
