[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155143#comment-15155143
 ] 

Gary Gregory commented on HTTPCLIENT-1665:
------------------------------------------

I've applied this fix:

{noformat}
commit -m "[HTTPCLIENT-1665] Regression in 
org.apache.http.entity.mime.MultipartEntity and 
org.apache.http.entity.mime.content.StringBody. Use ASCII when charset is 
null." -N 
E:/vcs/svn/apache/httpcomponents/branches/4.5.x/httpclient/httpmime/src/main/java/org/apache/http/entity/mime/content/StringBody.java
    Sending        
E:/vcs/svn/apache/httpcomponents/branches/4.5.x/httpclient/httpmime/src/main/java/org/apache/http/entity/mime/content/StringBody.java
    Transmitting file data ...
    Committed revision 1731313.
{noformat}

Merci [[email protected]]!

> Regression in org.apache.http.entity.mime.MultipartEntity and   
> org.apache.http.entity.mime.content.StringBody
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1665
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1665
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpMime
>    Affects Versions: 4.5
>            Reporter: Philippe Mouawad
>            Priority: Trivial
>              Labels: regression
>             Fix For: 4.5.2
>
>
> As per org.apache.http.entity.mime.MultipartEntity constructor documentation:
> > @param charset the character set to use, may be {@code null}, in which case 
> > {@link MIME#DEFAULT_CHARSET} - i.e. US-ASCII - is used.
> But it appears that in 4.5 version, if null is passed then no charset part is 
> written.
> The same issue exists for  FormBodyPart.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to