I haven't tried this but can you get the cookie from your first response (when cookie is created) and the re-submit it in the headers of your subsequent requests?
On Nov 11, 7:29 pm, anucekay <[email protected]> wrote: > Hi > > Our gadget primarily uses OAuth to authenticate with our system and > uses gadget.io.makeRequest calls to do REST calls to our server . > > Our production system which has a load balancer front-ending. > Our backend servers each have a cache which is specific to that JVM > ie. > (no distributed/clustered caching). We use the load balancer in > "sticky mode" (cookie based) so that the server initially selected > by > by LB is what is used for subsequent invocations. > > Up to now this hasn't been a problem > since all our network connections to the server are guaranteed to > return > to the same server that was initially selected by the Load > Balancer. > But if the Load Balancing scheme isn't followed so that two > consecutive > calls ends up in two different JVMs causing all kinds of issues. > > It looks like the gadget server is not preserving the cookies > across > OAuth and the actual service invocations. So we run into all kinds > of > problems from not being to conenct to consistency issues. > > Is this a known issue? Are there any workarounds or solutions? > > Anu -- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" 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/google-gadgets-api?hl=.
