Hi Barry,
You're right, it's must be a feature to avoid AppEngine "admin" headers
being cached by proxies, should have thought about it by myself :-)
Thanx a lot for helping.
François
On Monday, January 27, 2014 3:30:45 PM UTC+1, barryhunter wrote:
>
>
>>
>> Connected with an "admin" account,
>
>
>
> Connected with an "admin" account, caching seems to be disabled, at least
> on Chrome and Firefox.
>
I've seen this too.
I believe its a 'feature' - ie so the admin shouldnt see stale pages. To
make it easier to edit pages in CMS's etc.
But it might also be to help ensure that your 'secr
Hi Vinny,
Thanx for trying to help, I really appreciate what you do in this group.
The cache problem seems related to the fact that I'm connected on the site
as an adminstrator.
In incognito mode or connected with another "basic" account, it works fine,
resources are properly cached.
Connecte
Hi Francois,
As Nicolas said in this post:
https://groups.google.com/forum/#!topic/google-appengine/k3LrZodr-WA the
caching seems to be working correctly. I can see the proper Cache-Control
and Pragma headers in the response when I use Chrome's Developer Tools
screen. Are you still experiencing er
Hi everybody,
Do you know why cache headers are modified by Google Frontend servers?
Google prohibits my dynamically served static resources to be cached on
proxy and user sides.
For example, Google set the Expires header to this:
Expires: Fri, 01 Jan 1990 00:00:00 GMT
And Pragma and Cache-Con
