It seems that Tomcat ignores request.setCharacterEncoding. The request char encoding 
however can be set globally in server.xml, tag "Connector", attribute URIEncoding, e.g.


  |       <Connector port="8080" address="${jboss.bind.address}"
  |          maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
  |          enableLookups="false" redirectPort="8443" acceptCount="100"
  |          connectionTimeout="20000" disableUploadTimeout="true"
  |          compression="on" compressionMinSize="2048" 
compressableMimeType="text/html,text/xml"
  |          URIEncoding="UTF-8"
  |       />
  | 

My goodness, I spent two days two find that out :-( Why don't do the Tomcat developers 
follow the spec? Or at least write out a warning or throw an exception if I call 
request.setCharacterEncoding ("pleaseIgnoreMe")?

angry,
Marcus


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853864#3853864

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853864


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to