Delay in updating content at public links

[Bob Oliver Bigellow XLII]

We have a number of files which are available publicly by the public link...

http://commondatastorage.googleapis.com..........

Originally, when one of these files was updated, it would almost instantaneously be reflected at that link. However, lately, it can take 5 minutes... 10 minutes sometimes 15 minutes or more before the changes are reflected. The files are uploaded via the web-based Google Storage Manager.

If the file is accessed via the Google Storage Manager (private) link...

https://doc-123abc-456def-s-googleusercontent.commondatastorage.googleapis.com..........

It shows the most recent content... but visiting the public link...

http://commondatastorage.googleapis.com..........

Always returns the old file... even with refreshes... until 5-15 minutes later or more.

We've tried disabling the public link, then re-enabling it, to try to "force" this content to be updated sooner... doesn't seem to help.

Is this an intentional design change, or is this a problem that needs to be looked into?

[Navneet (Google)]

Can you look at the response headers and see if there's a Cache-Control: or Expires: header? 

--
You received this message because you are subscribed to the Google Groups "Google Storage for Developers" group.
To post to this group, send email to gs-dis...@googlegroups.com.
To unsubscribe from this group, send email to gs-discussio...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/gs-discussion?hl=en.

[Bob Oliver Bigellow XLII]

Yes.

Cache-Control: public, max-age=3600

[Bob Oliver Bigellow XLII]

And...

Expires: Fri, 27 May 2011 17:46:27 GMT

The file was uploaded via the web-based Google Storage Manager and was replaced (with an upload) via the web-based Google Storage Manager. Ideally, if there are any other configuration settings for the file that need to be tweaked, that it can be done so via the web-based Google Storage Manager. If this isn't possible at this time, no biggie... we'll code that... but I'm just wondering if this is expected behavior.

[Bob Oliver Bigellow XLII]

I should also clarify... the file with that particular expiration value has since refreshed, but it was uploaded approximately 1/2 hour ago and took more than 10 minutes to be refreshed.

[Navneet (Google)]

Yes, that's the default cache header we add when you use the Google Storage Manager for data. There isn't a way to override that today, but if you use gsutil, you should be able to specify your own value (or none at all).

- Navneet

On Fri, May 27, 2011 at 9:49 AM, Bob Oliver Bigellow XLII <iam...@gmail.com> wrote:

Yes.

Cache-Control: public, max-age=3600

[Bob Oliver Bigellow XLII]

Gotcha. Thanks for clarifying.