Hi Emlyn,
How long ago did you change your code? I just want to make sure it isn't a
question of propagation and it won't eventually go through.
I can confirm on my end I see the new code. Are you also certain that
whoever uses your app in Australia isn't using a different version?
Cheers
On
We've been seeing this too, we had assumed that there was an intentional
infrastructure change.
When deploying new app versions, static resources served through Google front
end are old assets for quite a while, where previously they update straight
away.
This is pretty bad for one page apps (
Your page is setting cache-control with a max age of 24hrs, so if it's been
less than that then things are working as they're supposed to - if you need
new content to be reflected more quickly, you should change the
cache-control. If you check the headers on the response and see a non-zero
'Age
Thanks Greg, that's really useful. We've had that setting (24 hour
expiry) for a long time, but I've never seen it actually honoured like
this (and weirdly only for Australia). But I'll file this under "not a
bug but a feature" and go fix our cache settings.
On 18 November 2015 at 07:28, Greg Jone
