*bump* The last time I posted this message it didn¹t gain any traction. However this is now affecting us in a production environment and forces us to import the certificate of the load balancer into our shindig server. Ideas?
On 6/1/11 3:33 PM, "Davies,Douglas" <[email protected]> wrote: > Our shindig server runs under https. It appears that the shindig server makes > a call back to itself for listMethods using > > "osapi" : { > "endPoints" : [ "https://%host%/opensocial/rpc"; ] > } > > from container.js (which I¹ve overridden with https and our webcontext). > > 1) Why does shindig call back into itself and not just make a function > call? Why doesn¹t it just use local host? This requires the certificate to > be installed and java made aware of it. > > 2) Some of these values seem to be used client-side as well as > server-side. If I remember right, when I changed it to > http://localhost/opensocial/rpc , then I had trouble client-side. Unfortunate > that the value is used for dual purposes.
