Hi there, I'm coming close to making my application live, and find myself worrying about how I'll safely roll out changes to it in the future.
My problem is that I can't use *.appspot.com alternative version URLs for testing, since the application relies on setting cookies that another component within a subdomain of my main domain needs to authenticate browser clients, and also to allow cross-IFRAME communications with that subdomain (see http://en.wikipedia.org/wiki/Same_origin_policy ). My setup is such: www.domain.com <- main application events1.domain.com <- component requiring cookies and same-origin. Accessing an alternative version via appspot.com will fail, since from a browser's perspective, events1.domain.com lies in a different security zone to appspot.com. The only thing I can think of is it set up a proxy server within domain.com, say, www-dev.domain.com, which rewrites the Host: header and passes the request on the alternative version running inside appspot.com, but I've suspicions that this setup won't work for as yet undiscovered reasons. I can disable same origin restrictions on AJAX in Firefox using a special about:config option, but this doesn't apply to Internet Explorer, and it also doesn't apply to setting cookies. Ideas? David. -- It is better to be wrong than to be vague. — Freeman Dyson --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
