It's not a bug, it is called "chunked encoding". Obviously your server is not HTTP 1.1 compliant or refuses chunked encoding. There is an option in Axis2 to turn that off. By searching the documentation or the mailing list, you will be able to find some examples.
Andreas On Wed, Jun 17, 2009 at 21:23, NathanDM<[email protected]> wrote: > > Here is some interesting information from a tcp trace. > > Request: > > POST /WebService1.asmx HTTP/1.1 > Content-Type: text/xml; charset=UTF-8 > SOAPAction: "http://cgx.com/Test"; > User-Agent: Axis2 > Host: localhost:1401 > Transfer-Encoding: chunked > > c1 > <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Body><Test > xmlns="http://cgx.com/"/></soapenv:Body></soapenv:Envelope> > 0 > > ====== > Response > > HTTP/1.1 400 Bad Request > Server: ASP.NET Development Server/9.0.0.0 > Date: Wed, 17 Jun 2009 19:03:33 GMT > X-AspNet-Version: 2.0.50727 > Cache-Control: private > Content-Length: 0 > Connection: Close > === > > The headers seem mild enough. However where is the c1 at the beginning and > the 0 at the end coming from? > > Another interesting data point. > > Trying to send some raw data through post - the same data minus the c1 and > the 0. Look at the result:] > > Request: > POST /WebService1.asmx HTTP/1.1 > Content-Type: text/xml; charset=UTF-8 > SOAPAction: "http://cgx.com/Test"; > User-Agent: Axis2 > Transfer-Encoding: chunked > Host: localhost:1401 > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Content-Length: 193 > > <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Body><Test > xmlns="http://cgx.com/"/></soapenv:Body></soapenv:Envelope> > > ==================================== > Response: > > HTTP/1.1 200 OK > Server: ASP.NET Development Server/9.0.0.0 > Date: Wed, 17 Jun 2009 19:06:27 GMT > X-AspNet-Version: 2.0.50727 > Cache-Control: private, max-age=0 > Content-Type: text/xml; charset=utf-8 > Content-Length: 328 > Connection: Close > > <?xml version="1.0" encoding="utf-8"?><soap:Envelope > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";><soap:Body><TestResponse > xmlns="http://cgx.com/";><TestResult>True</TestResult></TestResponse></soap:Body></soap:Envelope> > > ============================= > > Definitely the request is more useful without the c1 and the 0. I had 1.4.1 > and upgraded to 1.5 and they probably both had this problem. > > Where are these extra characters coming from? I would be willing to pay > twice as for a version of Axis that does not put those in there. ;) > > Nathan > > -- > View this message in context: > http://www.nabble.com/The-input-stream-for-an-incoming-message-is-null-tp24067861p24080290.html > Sent from the Axis - User mailing list archive at Nabble.com. > >
