SOAP and Chunked Transfer

[Eric]

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

[Dino Chiesa [Microsoft]]

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
"Eric" <fi****@earthling.net> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

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

[vgindin]

'Dino Chiesa [Microsoft Wrote:

;2329247']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
"Eric" <fi****@earthling.netwrote in message
news:%2****************@tk2msftngp13.phx.gbl...

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

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)
--
vgindin