On Fri, Mar 8, 2013 at 2:43 PM, Chris Geer <[email protected]> wrote: > All, I've been playing with the OpenSocial Gadget href support and have run > into an issue that I'm not sure is supported or not and if it is, if it's a > Rave or Shindig issue. OpenSocial allows module definitions like this: > > <?xml version="1.0" encoding="UTF-8" ?> > <Module> > <ModulePrefs title="Report"> > <Require feature="views" /> > <Require feature="open-views" /> > <Require feature="embedded-experiences" /> > </ModulePrefs> > <Content type="html" view="home" href="http://192.168.114.131:8080/Test > "/> > </Module> > > Where the gadget data is loaded from the href directly. That works great > for static pages however if that page also loads additional items like > javascript, the request doesn't seem to be proxied to the backend server > and returns a 404 error. I think the problem is with the links because if I > have my gadget XML at http://localhost:8080/xyz/test.xml it then looks for > any secondary files in the same place, which it won't find. I would think > all those URLs would need to be rewritten during the initial render to > point to Shindig/Rave so that the real resource can be proxied properly. > > Has anyone gotten this to work before?
I would look at the content re-writer: http://opensocial-resources.googlecode.com/svn/spec/2.5/Core-Gadget.xml#rfc.section.5 > > Chris
