Doug, I was also hacking up some code the other day that may be related.....
Instead of setting the API_HOST and API_PATH to go through the proxy, you can setup a transparent proxy running on the containers domain to just "forward" the requests on to the Shindig server. The proxy I was using was the one provided by Jetty, which may be convenient if you are using Jetty to run you app :) http://docs.codehaus.org/display/JETTY/Asynchronous+Proxy+Servlet -Ryan From: daviesd <davi...@oclc.org> To: <dev@shindig.apache.org>, Date: 03/26/2012 04:58 PM Subject: Re: Shindig running on different domain than container REVISITED One other thing (if it helps). I see gadgets that don't do makeRequest fail as follows: Unsafe JavaScript attempt to access frame with URL http://localhost:9090/opensocial-demo/testcontainer/ from frame with URL http://localhost:8080/opensocial/gadgets/ifr?url=http%3A%2F%2Fhosting.gmodul es.com%2Fig%2Fgadgets%2Ffile%2F112581010116074801021%2Fhamster.xml&container =default&view=default&lang=%25lang%25&country=%25country%25&debug=0&nocache= 0&sanitize=%25sanitize%25&v=d699982ddc921667a106a76c22bc8e22&testmode=0&pare nt=http%3A%2F%2Flocalhost%3A9090&mid=0#up_hamsterName=%25up_hamsterName%25&u p_bgColor=%25up_bgColor%25&up_bodyColor=%25up_bodyColor%25&up_earColor=%25up _earColor%25&up_snoutColor=%25up_snoutColor%25&up_eyeColor=%25up_eyeColor%25 &up_feetColor=%25up_feetColor%25&up_tailColor=%25up_tailColor%25&up_waterCol or=%25up_waterColor%25&up_foodColor=%25up_foodColor%25&up_wheelColor=%25up_w heelColor%25&up_wheelOuterColor=%25up_wheelOuterColor%25&up_wheelCenterColor =%25up_wheelCenterColor%25&up_wheelSpokeColor=%25up_wheelSpokeColor%25. Domains, protocols and ports must match. So it's obvious I'm gonna have lots of issues getting this working. Is cross-domain support on the roadmap anywhere? I can try to tackle this but if it's on someone's roadmap I'll live with the proxy solution in the meantime. doug On 3/26/12 4:38 PM, "daviesd" <davi...@oclc.org> wrote: > Ok, one step forward. If I add > > servletResponse.addHeader("Access-Control-Allow-Headers", "Content-Type"); > > It starts working and the gadget renders. Cool. But then the first makeRequest > from a gadget seems to be having difficulty. > > doug > >