You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Walco van Loon (JIRA)" <ji...@apache.org> on 2007/03/23 08:41:32 UTC
[jira] Created: (FILEUPLOAD-131) MultipartStream always assumes
transfer encoding to be BINARY
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
[jira] Commented: (FILEUPLOAD-131) MultipartStream always assumes
transfer encoding to be BINARY
Posted by "Walco van Loon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FILEUPLOAD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483451 ]
Walco van Loon commented on FILEUPLOAD-131:
-------------------------------------------
Also see https://issues.apache.org/struts/browse/STR-1528 for a more extensive explanation.
> 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
[jira] Commented: (FILEUPLOAD-131) MultipartStream always assumes
transfer encoding to be BINARY
Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (FILEUPLOAD-131) MultipartStream always assumes
transfer encoding to be BINARY
Posted by "Walco van Loon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FILEUPLOAD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485914 ]
Walco van Loon commented on FILEUPLOAD-131:
-------------------------------------------
If I understand correctly MIME is not in scope of httpcore, but I would think commons-mime would be a great idea!
> 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
[jira] Commented: (FILEUPLOAD-131) MultipartStream always assumes
transfer encoding to be BINARY
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FILEUPLOAD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487376 ]
Jochen Wiedmann commented on FILEUPLOAD-131:
--------------------------------------------
Question posted to httpcomponents-dev@jakarta, see http://www.nabble.com/Handling-content-transfer-encoding-encoding-and-multipart-requests-with-httpcomponents-tf3539561.html
> 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
[jira] Commented: (FILEUPLOAD-131) MultipartStream always assumes
transfer encoding to be BINARY
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FILEUPLOAD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485460 ]
Jochen Wiedmann commented on FILEUPLOAD-131:
--------------------------------------------
It is questionable, whether anyone is ready to add support for transfer encoding to the current framework. In other words, this issue can only be solved if someone takes the job to rewrite the parser to use an external library like Jakarta httpcore.
> 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