Re: Debugging

I have taken a quick look at this.  I believe the underlying cause is the code 
NuSOAP uses to 'deflate' the HTTP body.  This has come up before with both IE 
and Delphi, and is on my to-do list to investigate.

For whatever reason, Mozilla (I use 1.4.1) can inflate the body, as can, not 
surprisingly, NuSOAP.  When I point IE to an HTTP proxy, it does not send an 
Accept-Encoding header, NuSOAP does not deflate, and I see the response.

On a side note, IE includes the following HTTP header in the request

    Content-Type: application/x-www-form-urlencoded

NuSOAP will not complain that the content actually must be text/xml.  The 
absence of a charset= modifier means that NuSOAP will treat the body as UTF-8 
encoded.  I am not sure whether IE actually sends it as UTF-8, so I am not sure 
that non-ASCII characters will be handled properly.

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message ----- 
From: "Jan Horsman" <jan@xxxxxxxx>
To: <nusoap-general@xxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, May 13, 2004 5:49 AM
Subject: Re: [Nusoap-general] Debugging


I took al look on the ?debug=1 issue.

MS Internet Explorer 6.0 does indeed not show any output (blank window) 
on the 
http://eazypro.wild.net/interactive/_WebServices/PolicyInterfaceWebService.php?debug=1
 
url.

Mozilla Firefox 0.8 howerver shows the SOAP message and debug info! So 
this is a IE browser problem rather than a bug in NuSoap.

This is the output shown by Firefox:

//-------------------------------
    <SOAP-ENV:Envelope 
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
-
    <SOAP-ENV:Body>
-
    <SOAP-ENV:Fault>
<faultcode>Server</faultcode>
<faultactor/>
<faultstring>error in msg parsing:
xml was empty, didn't parse!</faultstring>
-
    <detail>
<soapVal xsi:type="xsd:string"/>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
-
    <!--

soap_server: entering parse_request() on 04:47 2004-05-13
soap_server: Accept: 
application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1
soap_server: Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
soap_server: Accept-Encoding: gzip,deflate
soap_server: Accept-Language: en-us,en;q=0.5
soap_server: Connection: keep-alive
soap_server: Host: eazypro.wild.net
soap_server: Keep-Alive: 300
soap_server: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; 
rv:1.6) Gecko/20040206 Firefox/0.8
soap_server: got character encoding: UTF-8
soap_server: parser debug:
soap_parser: xml was empty, didn't parse!

soap_server: leaving parse_request() on 04:47 2004-05-13
soap_server: Enter send_response

-->
<!-- Content being deflated -->
//-------------------------------


with kind regards,

Jan Horsman


Scott Nichol wrote:

>Your modification is a great way to make this work for you, so there is no 
>reason not to do it.  As you have seen, once you have stripped out the form 
>element name, you get text that is a valid SOAP payload.  NuSOAP does not 
>require a SOAPAction HTTP header, nor does it require that the Content-Type is 
>text/xml (which, technically, it should do), so you are saved from having to 
>finagle those.
>
>If the Content-Type contains a charset, it will use that as the character 
>encoding, otherwise it assumes UTF-8 encoding.  If you are sending non-ASCII 
>characters, this might affect you.
>
>I will look at the ?debug=1 issue later.
>
>Scott Nichol
>
>Do not send e-mail directly to this e-mail address,
>because it is filtered to accept only mail from
>specific mail lists.
>
>----- Original Message ----- 
>From: "Chris Boget" <chris@xxxxxxxx>
>To: <nusoap-general@xxxxxxxxxxxxxxxxxxxxx>
>Sent: Wednesday, May 12, 2004 12:42 PM
>Subject: Re: [Nusoap-general] Debugging
>
>
>  
>
>>My comments were based on the assumption that
>>    
>>
>[snip]
>  
>
>>was a standard SOAP endpoint.  If you have modified it to also
>>accept non-standard request formats, more power to you!
>>    
>>
>
>I didn't modify it very much.  Aside from one line, it looks *exactly*
>like the soap server example on the NuSOAP website:
>
>----------------
>  $sXMLString = isset( $HTTP_RAW_POST_DATA ) ? $HTTP_RAW_POST_DATA : '';
>  $sXMLString = eregi_replace( 'sXMLString=', '', $sXMLString );
>
>  $server = new soap_server;
>  $server->register( 'PolicyInterfaceWebService' );
>  $server->service( $sXMLString );
>-----------------
>
>That's it.  So if the soap_server shouldn't be able to work with the
>data that you are seeing within the textarea of the form then there is
>something else going on behind the scenes that I have no hand in.
>All I know is that once $sXMLString is passed into my function, it
>contains only the XML that is within the "<soap:Body>" node.
>
>But, all of this is tangential to my original problem/question which
>was regarding the fact that the debugging information is not being
>returned when debugging is turned on.  IE, why does the service
>not work when I set "debug=1" (in the query string or in the actual
>script) but it does work if I don't initialize the debug variable?
>For example, if you just go to
>
>http://eazypro.wild.net/interactive/_WebServices/PolicyInterfaceWebService.php
>
>straight out, you get a soap_server fault with the fault string being:
>
>"error in msg parsing: xml was empty, didn't parse!"
>
>But if you add on the "debug=1" query string
>
>http://eazypro.wild.net/interactive/_WebServices/PolicyInterfaceWebService.php?debug=1
>
>then nothing is returned back to the browser.  Why is that?  Based
>on what I've read within the code and based on emails that have
>been sent to the list on this subject, the above *should* work.  Yet
>it doesn't.
>
>Thank you for your time, assistance and continued patience.
>
>Chris
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Sleepycat Software
>Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
>higher performing products faster, at low TCO.
>http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
>_______________________________________________
>Nusoap-general mailing list
>Nusoap-general@xxxxxxxxxxxxxxxxxxxxx
>https://lists.sourceforge.net/lists/listinfo/nusoap-general
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Sleepycat Software
>Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
>higher performing products faster, at low TCO.
>http://www.sleepycat.com/telcomwpreg.php?From=dnemail3
>_______________________________________________
>Nusoap-general mailing list
>Nusoap-general@xxxxxxxxxxxxxxxxxxxxx
>https://lists.sourceforge.net/lists/listinfo/nusoap-general
>
>
>  
>




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click