Cross Domain issues in DEV Env.

[Xandeco, Maxwell]

Hi guys, how do you handle cross domain issues in development env?

I deployed the shindig in a standalone server: http://localhost:8080/ and want to run osec or my own container in another server (jetty:run) http://localhost:8081/portal.

But when i try to access some services from shindig, I got cross domain errors, that's expected, but how do you guys handle that to develop and test OSEC?

Thanks.

Maxwell

[Ciancetta, Jesse E.]

Hi Maxwell,

Hmm -- so it sounds like you're trying to send Ajax requests to your shindig server from code running on your container page? I don't think we've run into that issue -- I don't think we have anything on our container page that needs to talk to shindig from the client side using Ajax (we do have some backend Java code in OSEC that calls to shindig for gadget metadata, but that's about it I think).

In our environment the only code we have that makes Ajax calls to shindig is from within gadgets themselves, and in that case since the gadgets are calling back to their origin server its allowed.

Can you give us a little insight into what you're trying to do?

--Jesse

[Xandeco, Maxwell]

Hi,

I'm starting to use CommonContainer, that uses rpc to load gadgets metadata and put it in the container, is where I am getting cross domain issues, maybe I should override the "metadata fetcher" in CommonContainer and let my server handle the requests.

Thanks.

________________________________________
De: opensocial-ente...@googlegroups.com [opensocial-ente...@googlegroups.com] em Nome de Ciancetta, Jesse E. [jc...@mitre.org]
Enviado: segunda-feira, 14 de fevereiro de 2011 12:54
Para: opensocial-ente...@googlegroups.com
Assunto: RE: Cross Domain issues in DEV Env.