dotnet web services: SOAP and Chunked Transfer -- dotnet web services

You're in the

dotnet web services

group:

SOAP and Chunked Transfer

Eric
7/23/2004 11:29:06 PM

dotnet web services: Hi,

I have a .NET client and Java web service.

I send an request and the answer with a correct SOAP message.

But on the .NET client I get an exeption from the XML deserializer that he
has found characters which he doesn't understand.

When I look at the respond (via network monitor), I see that the message was
sent as chunked transfer coding (transfer-coding = "chunked").
The XML parser has problem with content length character before the XML
message (Exception is thrown in Invoke method). It seems that these
characteres are not filtered.

Where could be the problem?
Wrong encoding?
HTTP 1.0 used?

Does the .NET SoapHttpClientProtocol support 'chunked' HTTP messages?

Thanks
Eric

Re: SOAP and Chunked Transfer

Dino Chiesa [Microsoft]
7/27/2004 9:14:16 PM

I have had heisenberg issues related to this.
Using the network monitor actually changed the behavior I was seeing in some
cases. (not sure why, maybe just a broken network monitor). This doesn't
happen always, but I did battle it once.

But to answer your question, yes, .NET does support chunking.

-D

[quoted text, click to view]

Re: SOAP and Chunked Transfer

vgindin
12/8/2006 8:51:35 AM

[quoted text, click to view]

Hi, All. Dino, could you tell us how can we set http chunking up in our
web service? (.Net Framework 2.0 and WSE 3.0)

--

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet web services group.

home · blog · groups

Questions? Comments? Contact the dn