Re: Interfacing with SOAP or XML_RPC with javascript and HTML_AJAX
| From: | Joshua Eichorn | Date: | Wed, 25 Jan 2006 01:00:58 +0000 |
| Subject: | Re: Interfacing with SOAP or XML_RPC with javascript and HTML_AJAX | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-22672@lists.php.net to get a copy of this message | ||
If you do find any good articles on signing js code that actually work on IE and FF let me know. I'd be interested in having the resource links around for other people to handle it. I do however think that things like signed privileged code is going to something which is harder and harder to do over time, since signing doesn't prove your not malicious and it puts us squarely back into an activex style security hell.
-josh
Dan Rossi wrote:
I know sorry to even ask for that request ! Ok ill work with the raw XMLHttpRequest , there is this i found, but doesnt seem to want to work remotely just yet, i think i have to sign the scripts somehow, there is alot of talk about signing scripts but not talk on how ! http://www-128.ibm.com/developerworks/webservices/library/ws-wsajax/ On 25/01/2006, at 10:22 AM, Joshua Eichorn wrote:I thought it was because you were one of those crazy people who are trying to move web service stuff 100% to the client. Sounds like someone is asking for security problems down the road if they think any js soap client will be more secure then a PHP one. -josh Dan Rossi wrote:--PEAR General Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.phpYou prob misread the part where two customers have issues using our SOAP client. One their server has no route out to the internet, the other simply wont put the SOAP client and NuSoap scripts on their server because they are paranoid, so im stuck with having to come up with a javascript alternative which may only work in newer browsers lol. Why else would I be asking about this :\ On 25/01/2006, at 4:32 AM, Joshua Eichorn wrote:The proper way to handler this is too create a proxy on your server and have your server send the soap calls. You could add soap support to HTML_AJAX its "just" writing a new serializer. But any soap javascript serializer i've seen would be larger then the rest of HTML_AJAX. -josh Dan Rossi wrote:--PEAR General Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.phpOn 24/01/2006, at 3:31 PM, Justin Patrin wrote:--PEAR General Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.phpJustin thanks, well ideally the grab method in HTML_Ajax could be calling something remote, anything using XMLHTTPRequest an mozilla has this silly security problem, i have to spend extra time later to work out how to sign these scripts to get them to work. Im needing it to however do a remote call to a remote server, as the client will be accessing the main SOAP server. Ive looked into sending the soap messages using XMLHTTPRequest , but wanted a more streamlined solution to do it like HTML_Ajax also there is issues there protecting the key data for the clients having to send that in the javascript also as it will have to be called from an included php scripting outputting php variables or the xml message data however theres the issue there of resitrciting load access to that domain only. Ive already looked at the code project proxy example, i may have to build the proxy generator in php though as its in .NET also it only supports IE6 and above. Im looking at the second url now cheers. --PEAR General Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.phpAJAX *is* remote calls, although I have no idea if HTML_AJAX supports such a thing. I'm entirely sure that you can do it by creating the right XML document and sending it along, then parsing the response. In fact, from a quick Google search I see 2 possibilities already. http://www.codeproject.com/soap/JavaScriptProxy_01.asp?df=100&forumid=196063&exp=0&select=1260980 http://lists.xml.org/archives/xml-dev/200002/msg00435.html And security is what you make it. Call your webservice over SSL and it's encrypted. Make it use a login in the call and it's more secure. --