[jira] Commented: (CXF-2649) no content length in http header

["Daniel Kulp (JIRA)" <ji...@apache.org>]

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

Daniel Kulp commented on CXF-2649:
----------------------------------



You would need to use wireshark or something to get the raw transfer headers.    The Content-Length would not appear in the outgoing logging interceptor as the JDK HttpURLConnection would calculate that as part of what it does.   (which occurs after the logging out) 

In anycase, I cannot reproduce.  If I use your code above and look at the wireshark output, the Content-Length header is there.   

Also, roughly what size is the soap message being sent?



> no content length in http header
> --------------------------------
>
>                 Key: CXF-2649
>                 URL: https://issues.apache.org/jira/browse/CXF-2649
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.1.8, 2.2.5, 2.2.6
>         Environment: invoking .net (wcf) ws  deployed on iis
>            Reporter: Luca Di Stefano
>
> Even if I disabled the chunking, no content length field is added to http header.
> here the code for disable chunking
>         Client client = ClientProxy.getClient(as);
>         HTTPConduit http = (HTTPConduit) client.getConduit();
>         //Turn off chunking so that NTLM can occur      
>         HTTPClientPolicy httpClientPolicy = new HTTPClientPolicy();
>         httpClientPolicy.setConnectionTimeout(36000);
>         httpClientPolicy.setAllowChunking(false);
>         http.setClient(httpClientPolicy);
> here the logs:
> 03.02.10-18:24:02,922 [main] DEBUG phase.PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor@54a5f709
> 03.02.10-18:24:02,923 [main] DEBUG phase.PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.interceptor.StaxOutInterceptor$StaxOutEndingInterceptor@4f4a1ab7
> 03.02.10-18:24:02,923 [main] DEBUG phase.PhaseInterceptorChain - Invoking handleMessage on interceptor org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor@fa5e4e4
> 03.02.10-18:24:02,924 [main] INFO  interceptor.LoggingOutInterceptor - Outbound Message
> ---------------------------
> ID: 1
> Address: http://yule.prov.bz:8090/DPA/DpaService.svc?wsdl
> Encoding: UTF-8
> Content-Type: text/xml
> Headers: {SOAPAction=["http://www.dpa.com/AuthenticationService/Login"], Accept=[*/*]}
> Payload: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">......
> --------------------------------------
> 03.02.10-18:24:02,925 [main] DEBUG http.HTTPConduit - Response Code: 411 Conduit: {http://www.dpa.com}AuthenticationServicePort.http-conduit
> 03.02.10-18:24:02,925 [main] DEBUG http.HTTPConduit - Content length: 24
> 03.02.10-18:24:02,925 [main] DEBUG http.HTTPConduit - Header fields: 
>     null: [HTTP/1.1 411 Length Required]
>     Date: [Wed, 03 Feb 2010 17:24:03 GMT]
>     Content-Length: [24]
>     Content-Type: [text/html]
>     Connection: [close]
> ....
> javax.xml.ws.soap.SOAPFaultException: Response was of unexpected text/html ContentType.  Incoming portion of HTML stream: <h1>Length Required</h1>
> 	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
> 	at $Proxy59.login(Unknown Source)
> 	at it.bz.prov.egov.test.cxf.security.documentale.DocSecuredCxf.main(DocSecuredCxf.java:140)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.