cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Stollar (JIRA)" <>
Subject [jira] [Commented] (CXF-6805) cxf-rt-transports-http adds Content-Type header to GET request
Date Sun, 28 Feb 2016 18:30:18 GMT


Richard Stollar commented on CXF-6805:

There's the problem. I tried to find somewhere where I could set the 
property but couldn't work it out.

When the header is set then this is the stack-trace I receive:

    *Caused by: ParseError at
    Message: Premature end of file.
         ... 12 more*

*WSDLManagerImpl.loadDefinition(String url)*  must be where things start 
to go wrong. I couldn't find where the actual *Message* was being 
created in this flow. I'll look at it some more tomorrow.  I'm not 
really used to working with Maven projects and thus debugging this isn't 
something I have tried. I just rebuild the .jar files and re-run my test 
application with them - adding System.out.println() messages for debug.

Best regards,

Richard Stollar
See: My Site <>

> cxf-rt-transports-http adds Content-Type header to GET request
> --------------------------------------------------------------
>                 Key: CXF-6805
>                 URL:
>             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

View raw message