[
https://issues.apache.org/jira/browse/CXF-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701204#comment-14701204
]
Sergey Beryozkin commented on CXF-6538:
---------------------------------------
Hi Aki
The proxy issue is reported here: sorry, looks like the issue there is slightly
different but has been confirmed to be caused by a missing Content-Type.
If we have an empty POST or PUT then IMHO it is wrong to rely on
HTTPUrlConnection to set a form payload by default: Async/HttpClient conduit
does not do it and it was known to cause side-effects for servers that had
non-form Consumes.
Having the users to set something like Content-Type: application/json just to
get beyond HttpUrlConnection restriction appears to be not ideal to me
Cheers, Sergey
> Let users disable sending Content-Type with empty requests with URLConnection
> conduit
> -------------------------------------------------------------------------------------
>
> Key: CXF-6538
> URL: https://issues.apache.org/jira/browse/CXF-6538
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
> Priority: Minor
> Fix For: 3.1.3, 3.0.7
>
>
> If no Content-Type is set for empty requests then HttpUrlConnection:
> - sets a form Content-Type for empty POST
> - replaces custom Accept value with a wildcard if HTTP proxy is used
> To bypass it CXF sets a wildcard CT for empty requests which causes issues if
> the target server does not accept such a wildcard.
> CXF RS code can override it with a preferred CT if needed, but sending CT
> with GET is better be avoided so a new property
> "set.content.type.for.empty.request" is introduced (note no 'wildcard' in the
> property name to let us default to something else if needed).
> The property is set to true by default. If a user sets it directly to false
> then CT will be dropped. Hopefully this property can be disabled by default
> in the future.
> Note the issue applies to a default non-async conduit only. Setting the
> property is not needed if it is the async conduit.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
