AllowChunking on the client-side applies purely to the transfer encoding of outgoing requests.
Willingness to receive chunked responses is implicit in HTTP/1.1 support, so there's no way for a HTTP/1.1 client to communicate with a server its preference to receive unchunked responses, e.g. you can't do "Accept-encoding: !chunked" Cheers, Eoghan 2009/12/9 Glen Mazza <[email protected]> > > Hello, does the AllowChunking client-side config element[1] control whether > the web service provider will chunk back SOAP responses to the client, or > is > it strictly just for the SOAP requests sent by the client? I'd like to > know > if the SOAP client can guarantee a Content-Length HTTP header from the web > service provider just by disabling this option on its end (normally > shutting > off chunking populates this header instead.). > > Thanks, > Glen > > [1] http://tinyurl.com/yzhf8ta > -- > View this message in context: > http://old.nabble.com/Client-side-%22AllowChunking%22-also-for-SOAP-responses--tp26705140p26705140.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
