You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2016/02/28 13:52:18 UTC

[jira] [Commented] (CXF-6805) cxf-rt-transports-http adds Content-Type header to GET request

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

Sergey Beryozkin commented on CXF-6805:
---------------------------------------

Hi, 

the code which initiates a WSDL query needs to set a an EMPTY_REQUEST_PROPERTY to true so that the branch checking if GET should have CT set or not runs (that branch does exclude CT for GET by default). The reason for it is that some legacy services do need GET + CT, example:

http://cxf.547215.n5.nabble.com/WebClient-Content-Type-Override-td4640790.html#a5765946

Can you please create another patch, somewhere where a WSDL query starts, there should be a code which sets EMPTY_REQUEST_PROPERTY to true. 

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