Honestly, you may just need to turn off chunking. When you say "smaller request succeeds", do you mean under 4096? If so, we automatically don't chunk for messages that small and just send a content-length header.
Dan On Wed February 10 2010 9:56:31 am Jim Talbut wrote: > Hi, > > I don't think this is a CXF problem, but it might be, or someone else > here might have experienced it and be able to help me out. > I'm using a CXF client to communicate with a .net web service running > on IIS 6. This request (anonymised): > > POST /EngineWebService_v1/EngineWebService_v1.asmx HTTP/1.1 > Content-Type: text/xml; charset=UTF-8 > SOAPAction: "http://.../Report"; > Accept: */* > User-Agent: Apache CXF 2.2.5 > Cache-Control: no-cache > Pragma: no-cache > Host: uat9.gtios.net > Connection: keep-alive > Transfer-Encoding: chunked > > followed by 7 chunks of 4089 bytes and one of 369 bytes, generates the > following output after the first chunk has been sent: > > HTTP/1.1 404 Not Found > Content-Length: 103 > Date: Wed, 10 Feb 2010 13:00:08 GMT > Connection: Keep-Alive > Content-Type: text/html > > AspEnableChunkedEncoding is enabled and a smaller request succeeds, so > it's not a real 404. > Anyone else found this problem and got a workaround? > > Thanks > > Jim > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. -- Daniel Kulp [email protected] http://www.dankulp.com/blog
