The proxy in shindig is mostly transparent, but nothing is guaranteed. If you absolutely must have complete control over headers you may need to set up a proxy of your own.
On Tue, Sep 7, 2010 at 11:19 AM, Randy Hudson <[email protected]>wrote: > On Sep 1, 12:08 pm, Paul Lindner <[email protected]> wrote: > > Unless you take specific actions your script could get cached by an > > opensocial container (or a corporate proxy for that matter) > > Thanks Paul. The URL already incorporates a hash that is unique the > the *expected* set of request headers. My concern is that I won't > even receive those headers because the browser is no longer the client. > > -- > You received this message because you are subscribed to the Google Groups > "OpenSocial Application Development" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<opensocial-api%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/opensocial-api?hl=en. > > -- Paul Lindner -- [email protected] -- linkedin.com/in/plindner -- You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en.
