1. From the request, one can tell the user uses gSOAP
User-Agent: gSOAP
2. I am amazed/amused that NuSOAP processes the request at all, considering the
presence of the <ORION>
elements around the SOAP envelope. With those present, this is not a valid
SOAP request.
3. Every SOAP RPC request should have a namespace associated with it. That
namespace should be on the element with the method name. NuSOAP happens to be
very permissive and allows requests to not specify the namespace, but the
request you show below should have a namespace.
4. The empty namespace in your response below should be acceptable to the
client. However, your user is correct that NuSOAP should not simply use the
namespace that it received in the request, but should use a namespace
configured by its own code.
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: "Jon Drukman" <jsd@xxxxxxxxxxxxx>
To: <nusoap-general@xxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, December 15, 2005 2:43 PM
Subject: [Nusoap-general] namespace changes on 0.7.2
> hi there. i'm not much of a SOAP guru, but i can pretty much get basic
> stuff to work with NuSOAP. one of our partners is complaining that an
> upgrade from NuSOAP 0.6.6 to 0.7.2 has broken things because of the way
> namespaces work now. in particular he claims that:
>
> "OK, I see what’s been changed. In the past, the <authenticate> element
> was not part of a namespace. It looks like you’ve changed it to use a
> namespace (<ns4515:authenticate xmlns:ns4515="http://tempuri.org">) and
> then return the same URI as what is passed, which rather defeats the
> entire purpose of namespaces."
>
> here's an example request/response that is giving them grief: (i've
> tidied up the indentation a bit to make it readable, hope that doesn't
> matter)
>
> Request:
>
> POST /rps/gamecenter/authenticate_gamecenter.php HTTPS/1.0
> Host: SCI
> SOAPAction: ""
> User-Agent: gSOAP
> Content-Type: text/xml; charset=utf-8
> Content-Length: 255
>
> <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
> <ORION>
> <SOAP-ENV:Envelope>
> <SOAP-ENV:Body>
> <authenticate>
> <name xsi:type="xsd:string">testuser</name>
> <pass xsi:type="xsd:string">testpass</pass>
> </authenticate>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> </ORION>
>
>
> Response:
>
>
> HTTP/1.1 200 OK
> Date: Wed, 14 Dec 2005 22:53:56 GMT
> Server: NuSOAP Server v0.7.2
> Set-Cookie: sess=88596253D%2500%2500; path=/; domain=.gamespot.com
> Set-Cookie: ptoke=db455d444017cf58; expires=Sat, 12-Dec-2015 22:53:56
> GMT; path=/; domain=.gamespot.com
> Host: myserver
> X-SOAP-Server: NuSOAP/0.7.2 (1.2)
> Content-Length: 1044
> Connection: close
> Content-Type: text/xml; charset=ISO-8859-1
>
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <SOAP-ENV:Envelope
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
> <SOAP-ENV:Body>
> <ns1:authenticateResponse xmlns:ns1="">
> <return>
> <cookie>
> <accessLevel xsi:type="xsd:string">cCA=</accessLevel>
> <gs_info xsi:type="xsd:string">MmewfSRUtIWlj2wwCA==</gs_info>
> <MDAAuth xsi:type="xsd:string">MGMxNWM5YTViNjdmYTg5NzdA==</MDAAuth>
> </cookie>
> <emailAddress xsi:type="xsd:string">gc01@xxxxxxxxxxx</emailAddress>
> <registrationId xsi:type="xsd:string">2772943</registrationId>
> <userName xsi:type="xsd:string">GCTest</userName>
> <regSource xsi:type="xsd:string"></regSource>
> </return>
> </ns1:authenticateResponse>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
>
> all i know is that it works fine with php nusoap and perl's soaplite. i
> don't know what client they are using to consume this, but i think they
> rolled their own. is this guy off base on the namespace thing? i don't
> really understand the issue and would love to just tell him to get
> stuffed if possible :)
>
> -jsd-
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Nusoap-general mailing list
> Nusoap-general@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/nusoap-general
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
|