[
https://issues.apache.org/jira/browse/CXF-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171764#comment-15171764
]
Sergey Beryozkin commented on CXF-6805:
---------------------------------------
The first commit went to the trunk,
http://git-wip-us.apache.org/repos/asf/cxf/commit/a669400f
Going to merge to the branches next, what I suggested earlier (force the client
GET code to set an empty request property just to make sure CT is not set) was
sub-optimal
Thanks
> cxf-rt-transports-http adds Content-Type header to GET request
> --------------------------------------------------------------
>
> Key: CXF-6805
> URL: https://issues.apache.org/jira/browse/CXF-6805
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.2.0
> Reporter: Richard Stollar
> Priority: Minor
> Attachments: cxf-rt-transports-http.patch
>
>
> Then generating a web service client from WSDL the request sent to the server
> has an additional Content-Type header. Microsoft IIS 6.0 fails to process
> these requests and returns 200-OK with empty body.
> The Content-Type header should not be added to the http request when the
> method is GET.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
