commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20813] - FileUpload does not take 'charset' parameter of the 'Content-Type' header into consideration
Date Fri, 12 Sep 2003 14:54:18 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20813>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20813

FileUpload does not take 'charset' parameter of the 'Content-Type' header into consideration





------- Additional Comments From olegk@apache.org  2003-09-12 14:54 -------
One may argue that RFC2046 should take precedence in this particular case, but I
agree that ISO-8859-1 is most likely to be expected by the users as a default
HTTP content encoding

Anyways, the patch is wrong in using default system encoding when no charset
explicitly set. I'll tweak the patch and submit an updated version this weekend.

Oleg

Mime
View raw message