Transfer-Encoding chunked and WCF

M

Martijn van Schie

I’m invoking a method on a 3rd party webservice using a WCF service client.
Everytime I invoke the method from code, no error occurs but my response
object is NULL.
Examining the reponse in fiddle shows me a response

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Wed, 06 Jan 2010 14:30:12 GMT

143f
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instanceâ€><CONTENT…></soapenv:Envelope>
0

The response has a header of encoding chunked. The only thing I can find on
the internet is that WCF does not support this.

I have been playing around with the messageEncoding (Mtom etc.) and
transferMode (Buffered) settings of the client config but no result.

I tried it using a 2.0 web service client proxy, and then it works.

Any idea’s how to resolve this.
 
A

Alvin Bruney - ASP.NET MVP

If it say it succeeded, it likely really did succeed.
Try http protocol, I don't see why this should fail if web services is
working. Perhaps it is the way you cast the returned object? Show so code.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top