Hi Josh
Thanks a lot for the update! As far as I understood, the cache-control
needs to be made on my server, right? Or is there a way to directly
control cache within my kml file? I would prefer the second option!
Another question: If I would use onExpire, this would mean, that I
always need to update the expiring date/time in the file?
As I am not a html/kml guru, it would be of great help, if you could
add some short info on how to best modify my original file or put in
here some brief example.
Many thanks in advance!!
Cheers, Albert
On 19 Aug., 19:06, Josh L wrote:
> Hey Albert,
>
> This looks like a caching issue. Since you are using Update without
> any additional/unique parameters in the URL, Google Earth makes a
> request for the same URL, and depending on your cache-control related
> headers may just use the locally stored cache of the file if the
> headers say that no update is needed.
>
> To solve this you may wish to modify your response cache-header to
> something like 'no-store', or use onExpire instead of onInterval and
> set your max-age header appropriately.
>
> Down the line, if you want to be able to scale to more complex
> updates, you may wish to use an incremental update strategy, like the
> one outlined athttp://
code.google.com/apis/kml/documentation/kml_21tutorial.html#upd...