hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Tobin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HTTPCLIENT-1112) HttpClient JSF issue - missing line feed character causes JSF file upload parse to fail.
Date Mon, 01 Aug 2011 01:15:09 GMT
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
             Fix For: 4.1.2


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 
the content body.   
The HTTPMime Java code definitely writes out the last dash dash CR and LF  i.e. "--\r\n" into
its internal buffers... but the generated final output stream is one byte short.  
>From a useability perspective this does not affect HTTP Client as it is able to read mime
multipart missing the linefeed... but it does affect other non http lcienconsumers of the
generated data, 


--
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


Mime
View raw message