DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36814>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36814 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-27 13:32 ------- it always comes down to what the servlet specification says a container implementation should do, what developers expect container implementations to do and how they should behave, and what developers often get confused about. character encoding seems to be one of those things that many developers are getting confused about, and this issue in particular seems to come about quite often. i suppose as far as a developer is concerned whatever data they send to the server should be maintained in that way. so if arabic is sent via a post running on tomcat, is it acceptable for the developer to have to understand that tomcat runs in a charset that is not universal and to have to seek a filter or write their own filter to change this? personally, i believe encoding falls into the same kind of category as other configuration elements like databases, jndi environment vars. imo the container should help out the developer with this type of functionality, if not by configuration, then by providing default configurable filters across web applications. just my opinion. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
