Win a copy of Practical SVG this week in the HTML/CSS/JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Anything wrong with the SOAP return?

 
Kerry Licari
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

The following is a web services return that intercepted by tcpmon.

web services is on axis 1.1
client: .net
style: document/literal

message:
--------------------------------------------------------------------
HTTP/1.1 100 Continue



HTTP/1.1 200 OK

Content-Type: text/xml;charset=utf-8

Transfer-Encoding: chunked

Date: Sat, 12 Feb 2005 16:00:58 GMT

Server: Apache-Coyote/1.1



13e

<?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">
<soapenv:Body>
<stringTestReturn xmlns="">Axis</stringTestReturn>
</soapenv:Body>
</soapenv:Envelope>

0

---------------------------------------------------------------------------


Could somebody tell me what are '13e' and '0' in the above message? The .net client didn't receive the return value from axis. Could that be caused by these two - the '13e' and '0'? (probably .net gets confused to deserialize the return response). How can I get rid of it?

Many thanks.
 
Lilly Wiesie
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The "13e" and "0" are for chunk encoding. It won't cause problems on .net side.
 
Get out of my mind! Look! A tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!