Caching is a best effort attempt to reduce load and should never be
thought of as a foolproof mechanism to prevent requests from hitting your
server. In the case you are describing, URL parameters still work since they
prevent the proxies and browsers from storing things they shouldn't store.
Most
Ah, interesting argument. I've never personally been in a situation where
we've had to replace CSS referenced images enough times that manually
changing their URIs was a problem, even in environments where I was
deploying 5+ times a day. In practice, every time I've used CSS referenced
images,
The tradeoff with request parameters is that you need to output your image
and asset tags in your HTML templates to append a parameter and be version
aware. The benefit, however, is that it is an almost 100% foolproof way to
bust caches. You don't only have the Google edge cache to worry about -
Can you guys run a traceroute on your domains vs. the appspot domain?
E.g:
traceroute qa.connectscholar.com
traceroute charityaxis-qa.appspot.com
If you're on Windows, the equivalent command is tracert.
I'm curious if there's an ISP or specific Google Frontend that is acting up.
On Thu, Jun
This probably is still occurring. Just out of curiosity - is your ISP
Comcast?
On Fri, Jun 4, 2010 at 4:56 AM, J j.si...@earlystageit.com wrote:
A couple of closing-out notes from our vantage point in Massachusetts.
First, even though the cache for one of our files was not supposed to
expire
Hey guys,
I've tracked this down, and it is working as intended. Our infrastructure
may or may not respect your cache headers and just cache assets for your
application. It's clear that's what's happening here, with some front-ends
caching and some not caching. The worst case scenario is that
Tim, can you provide 2 URLs that are doing this?
I'm still trying to reproduce the problem. Could an ISP be caching these
files?
On Thu, Jun 3, 2010 at 10:02 AM, Tim Hoffman zutes...@gmail.com wrote:
Hi
Not to bad an idea.
At the moment all of our templates use '/css/some_file.css'
rather
Partially off-topic--- if GFE serves a cached resource, do we get billed
for the bandwidth?
On Wed, Jun 2, 2010 at 3:27 PM, Ikai L (Google) ika...@google.com wrote:
Okay, looks like the Google Front-End is kicking in to cache your stuff
Server Google Frontend
Content-Length 2834
Age
Thanks for bringing this up, Tim. Anyone else seeing this problem? If so,
please post details. Are you guys setting any kind of cache headers?
I'm going to try to reproduce these issues, so any information will be
helpful.
On Wed, Jun 2, 2010 at 9:14 AM, J j.si...@earlystageit.com wrote:
On Wed, Jun 2, 2010 at 3:37 PM, J j.si...@earlystageit.com wrote:
To reproduce the problem, go to
http://qa.connectscholar.com/stylesheets/caSkin.css
and also to http://charityaxis-qa.appspot.com/stylesheets/caSkin.css.
Both URLs point to the same file but one returns the old content and
I wonder if there is some layer of the infrastructure that is performing
caching without you guys having opted-in, hence the reason why a
cache-buster like ?v=something works. Can you guys confirm? Also - are you
guys setting any headers? Which headers get returned?
I've personally always used
Okay, looks like the Google Front-End is kicking in to cache your stuff
Server Google Frontend
Content-Length 2834
Age 41
Cache-Control public, max-age=600
Are you guys setting this header anywhere? Unfortunately, there's no way to
invalidate items in the frontend cache, so you'll have
Okay, looks like the Google Front-End is kicking in to cache your stuff
Server Google Frontend
Content-Length 2834
Age 41
Cache-Control public, max-age=600
Are you guys setting this header anywhere? Unfortunately, there's no way to
invalidate items in the frontend cache, so you'll have
In the meantime, I'll investigate whether these headers are being implicitly
or incorrectly set.
On Wed, Jun 2, 2010 at 12:37 PM, J j.si...@earlystageit.com wrote:
Thanks, Ikai, for your help. It is much appreciated.
We'll use a cache buster for now.
On Jun 2, 3:27 pm, Ikai L (Google)
I can't reproduce this. Here's my YAML file:
application: ikailan-com
version: 1
runtime: python
api_version: 1
default_expiration: 1d
handlers:
- url: /
script: main.py
- url: /assets
static_dir: assets
Can you guys post your app.yaml?
On Wed, Jun 2, 2010 at 1:04 PM, Ikai L (Google)
15 matches
Mail list logo
