You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2003/11/07 09:43:17 UTC
DO NOT REPLY [Bug 20815] -
FileUpload always assumes transfer encoding to be BINARY and does not properly handle 'Content-Transfer-Encoding' header
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=20815>.
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=20815
FileUpload always assumes transfer encoding to be BINARY and does not properly handle 'Content-Transfer-Encoding' header
hauser@acm.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andres.meyer@computer.org,
| |hauser@acm.org
Status|RESOLVED |REOPENED
Priority|Other |High
Resolution|LATER |
------- Additional Comments From hauser@acm.org 2003-11-07 08:43 -------
I second Oleg in the plea to address this.
on p9, http://www.ietf.org/rfc/rfc1867.txt even gives an example where the
Content-Transfer-Encoding header is used!
I had the same problem with struts:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24465
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org