[
https://issues.apache.org/jira/browse/HTTPCLIENT-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876198#action_12876198
]
Doua Beri commented on HTTPCLIENT-950:
--------------------------------------
Hi Oleg. Thanks for your reply. Well the problem is that the website I wanted
to use has some problems if the header Content-Transfer-Encoding was send which
is the case of the strict mode. After that I tried with BROWSER_COMPATIBLE
thinking that this will solve my problem, but in BROWSER_COMPATIBLE mode the
content-type header is not sent. I know that most of the sites are not build
to accept standard specification, and probably the developers test them using
the common browsers ( firefox, internet explorer - where the content-type is
sended for files but they don't send the Content-Transfer-Encoding header)
But if you say this will change the logic of the BROWSER_COMPATIBLE mode that
it's ok. It seems that I misunderstood the purpose and thought this is a bug.
Catalin
> HttpMultipartMode.BROWSER_COMPATIBLE -- for files doesn't send Content-Type
> ------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-950
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-950
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpMime
> Affects Versions: 4.0.1
> Reporter: Doua Beri
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When you want to send files using HttpMultipartMode.BROWSER_COMPATIBLE it
> seems that the Content-Type is ignored. It seems that the browsers( tested
> with firefox and Internet explorer) are sending the content-type header only
> for files.
> It seems that some sites are sensitive about this issue and they choose the
> content-type for a file as a text/plain in case I don't specify one.
--
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: [email protected]
For additional commands, e-mail: [email protected]
