I have an app that sits behind a reverse proxy serving requests for multiple domains using the X-Forwarded-For header. This has been working very well for many months. Yesterday, after enabling billing for the app, I started seeing dynamic requests that were getting served the wrong content (content for the wrong domain).
In troubleshooting the issue, I noticed that many of the problem requests are served in only a couple of milliseconds, and the logs don't contain the normal logging messages that my code should produce, and don't show up in appstats. I'm assuming this means that the caching I've read about but never seen to work is now serving requests (since the Cache-Control header is set), and is not keeping cached pages separate based on the X-Forwarded-For header, but just the path. Is there any way to confirm whether this is what is happening? If so, is there a way to disable this functionality (going back to the way it worked before we enabled billing), without removing the Cache-Control header and losing it's benefits? -Mike -=- -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en.
