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...
> 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...
> 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?
> -- > 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-discussion@googlegroups.com. > To unsubscribe from this group, send email to > gs-discussion+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/gs-discussion?hl=en.
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.
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.
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:
> -- > 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-discussion@googlegroups.com. > To unsubscribe from this group, send email to > gs-discussion+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/gs-discussion?hl=en.