Re: Migrating to XML_RPC - SSL question

Indeed, thanks. I've been doing some testing and using SSL seems to be troublesome, at least with the versions of PHP I have on my servers. In some versions, fsockopen will only accept an address, not a URL, but XML_RPC appears to read the protocol from the URL to decide if it needs to go SSL or not. Forcing it onto port 443 just results in a regular HTTP transaction being attempted with the secure server, which obviously fails. Because of that issue it's still not clear to me whether SSLVerifyPeer would be a problem or not. At the moment this all looks a bit perilous so I don't think I'll migrate after all. I'll try again later when I've upgraded the version of PHP on the server! Jeff In article <432beae0511302145u74a4bce8obd7a371a9a24b19a@mail.gmail.com>, papercrane@gmail.com (Justin Patrin) wrote: > On 11/29/05, Jeff Tupholme <jeff@makemyshow.com> wrote: > > Hi, > > > > I'm migrating to XML RPC from the original phpxmlrpc 1.0.99 by Edd > > Dumbill. > > > > Mostly it has been easy, with just the method names needing changing. > > However, I sometimes use SSL and with the old library I used the method: > > > > xmlrpc client->setSSLVerifyPeer(0) > > > > This was ultimately passed through to cURL and gave some fine-grained > > control over how the SSL interaction took place. > > > > There doesn't seem to be an equivalent of this in the PEAR version, and > > I wonder what its default behaviour is? Is there a plan to add this > > functionality back in, or is there a reason why it is not needed? > > > > Thanks for any clarification anyone can offer. I don't want to cut over > > to the new version without fully understanding the implications. > > > > Well it looks like XML RPC uses fsockopen to make its calls, not curl, > so the same kind of thing won't work. I'm not sure how you'd fix > certificate problems with fsockopen. > > -- > Justin Patrin