Odd numbers in Axis 1.1 response

[Dan Ciarniello <dc...@cityxpress.com>]

In trying to resolve problems accessing an Axis service using .NET, I 
noticed some odd numbers in the response that Axis sends out.

I used TCPMon to look at the response message.  When I use a 
WSDL2Java-generated client, I get back a response like this:

HTTP/1.1 200 OK
Set-Cookie: JSESSIONID=5FE83FA540716220B0E8D09755947CC6; Path=/v01
Content-Type: text/xml;charset=utf-8
Date: Fri, 08 Oct 2004 18:02:26 GMT
Server: Apache-Coyote/1.1
Connection: close
 
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope ...>
</soapenv:Envelope>

However, if I just hand-craft a SOAP request, TCPMon shows the following 
response:

HTTP/1.1 200 OK
Set-Cookie: JSESSIONID=B5D9BA9C63E8C6542B0D97EDDAA67718; Path=/v01
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Fri, 08 Oct 2004 18:04:14 GMT
Server: Apache-Coyote/1.1
 
946
<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope ... >
</soapenv:Envelope>
0
 

 Note the 946 preceding the envelope and the 0 following.  Does anyone 
have any idea why these are there?  Why aren't they there when accessed 
with the generated code?  Could these be a reason for the trouble with .NET?

Thanks,
Dan.

Re: Odd numbers in Axis 1.1 response

[Nelson Minar <ne...@monkey.org>]

>Note the 946 preceding the envelope and the 0 following.  Does anyone 
>have any idea why these are there?

That's HTTP/1.1 chunked encoding. The other tipoff is
  Transfer-Encoding: chunked
It's a good thing.

>Why aren't they there when accessed with the generated code?

Probably because the request is specified differently.

>Could these be a reason for the trouble with .NET?

Dunno. You'd hope not!