Hi Toshiyuki and Yves,
Thanks. I never really worried about them, as they didn't affect my
services at all, but at least I know where they come from now.
Richard.
Toshiyuki Kimura wrote:
Hi Clarence and Richard,
It's valid transfer encoding - 'chunked' which is
specified in HTTP 1.1 [RFC-2616].
<http://www.w3.org/Protocols/rfc2616/rfc2616.html>
Thanks,
Toshi
On Tue, 15 Nov 2005, Richard Gregory wrote:
Hi Clarence,
I get these random numbers in my http when I connect
to my axis service with .NET clients. I'm not sure
where they come from or why, but they don't seem to
have any effect on the clients, which work perfectly.
Richard.
Clarence Dahlin wrote:
I've almost only used Axis for both client and server, but I also
need to verify that my service works with Visual Studio and other
toolkits.
I receive a somewhat puzzling HTTP Response when I've called the
service on Axis from a C# client in Visual Studio .NET.
I'm not getting the connectReturn to my client.
Does anyone know where the numbers 177 and 0 appears from and why?
Could they mess up things for my client?
HTTP/1.1 200 OK
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Tue, 15 Nov 2005 09:34:27 GMT
Server: Apache-Coyote/1.1
177
<?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";
<http://www.w3.org/2001/XMLSchema-instance%22>><soapenv:Body><connectResponse
xmlns="xxxi.xxx.se
<http://xxxi.xxx.se>"><connectReturn>c017e9/107931de21a//7ff8</connectReturn></connectResponse></soapenv:Body></soapenv:Envelope>
0
