One small piece of the puzzle - through playing around with the curl
--trace option in the terminal, I was able to discover that the
certificate it uses is:
/usr/share/curl/curl-ca-bundle.crt (this is Mac OS 10.4.6, presumably
this will be fairly consistent on macs).
Setting the sslcertificates to this now means that I can get the wsdl
without using the shell, and with verification on, though every other
attempt (or thereabouts) times out.
Still, this is progress!
best,
Mark
On 26 May 2006, at 14:32, Dave Cragg wrote:
Dave Cragg wrote:
It seems the secure socket is being opened OK (at least the Rev
engine thinks so), and the timeouts are occurring on the first
read immediately after writing the request.
On further checking, it seems the first write to the socket
(writing the request headers) is timing out. Also happening on OS X
10.3.9.
I've Bugzilla'd this (#3639).
Cheers
Dave
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
