You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2011/08/03 13:26:27 UTC
[jira] [Resolved] (HTTPCLIENT-1112) HttpClient JSF issue - missing
line feed character causes JSF file upload parse to fail.
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-1112.
-------------------------------------------
Resolution: Invalid
Fix Version/s: (was: 4.1.2)
I reviewed the source and found no evidence of HttpMime code miscalculating Content-Length value.
Feel free to re-open the issue if you can reproduce the problem with a test application independently from the JSF library.
Oleg
> HttpClient JSF issue - missing line feed character causes JSF file upload parse to fail.
> ----------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1112
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1112
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpMime
> Affects Versions: 4.1.1
> Environment: Any environment.
> Reporter: Kevin Tobin
> Labels: newbie
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We have an application that cannot read the mime multipart generated by HttpClient's HttpMime library but can read mime created by any other browser. Turns out that the only difference between the HttpClient mime multipart data is a missing linefeed at the very end of the content body.
> The end of the mime multipart should be a --\r\n, However, HttpClient outputs the carriage return character " hex 0D" but not the last line feed "hex 0A".
> We are using an IBM JSF library that could not parse the mime multipart but even worse - did not even report an error - so we spent a couple of days tracking down the problem.
> In the org.apache.http.entity.mime.HttpMultipart.java code - we can see that the class definitely writes out the last dash dash CR and LF i.e. "--\r\n" into its internal buffers... however the generated final output stream delivered across the network is one byte short - i.e. missing the linefeed. It's as if the internal Content-Length should be one byte longer.
> Our Apache File Upload code works fine with the missing linefeed generated mime data however the IBM JSF code does not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org