commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FILEUPLOAD-131) MultipartStream always assumes transfer encoding to be BINARY
Date Mon, 02 Apr 2007 08:29:32 GMT

    [ https://issues.apache.org/jira/browse/FILEUPLOAD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485970
] 

Oleg Kalnichevski commented on FILEUPLOAD-131:
----------------------------------------------

Folks,

I doubt HttpCore would be of any use here, as it does not (and is not supposed to) provide
any content codecs.  You probably may want to take a closer look at Commons Codec, which provides
two content transfer codecs mentioned in RFC1521: quoted-printable and base64. Some efforts
will have to spent on getting those codecs to work with I/O streams, though.

Oleg

> MultipartStream always assumes transfer encoding to be BINARY
> -------------------------------------------------------------
>
>                 Key: FILEUPLOAD-131
>                 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-131
>             Project: Commons FileUpload
>          Issue Type: Bug
>         Environment: N/A
>            Reporter: Walco van Loon
>
> MultipartStream always assumes transfer encoding to be BINARY and does not handle 'Content-Transfer-Encoding'
header at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message