You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Date is the time of downloading and last-modified seems to change every 30 minutes. It would be best, if this information were available in the header sent by the server. Of perhaps in a separate text/json file on the server.
The text was updated successfully, but these errors were encountered:
So in fact it is a new image every 30 minutes. So I guess it would require more work to determine if the base images have changed and store this information somewhere.
Hi @jmozmoz - yes, this is a good idea. Ostensibly the source data is updated every three hours, but the workflow runs more frequently because sometimes the base images contain holes which later get filled in.
What I could do is take a hash of the newly generated file, compare it to the currently published file, and only republish if it's changed. Then the last-modified should be accurate and you could issue a HEAD request to determine if you need to refetch.
Is there a way to access the creation time of the images? By this one could wait 3 hours before downloading a new file.
Currently the images do not contain EXIF data and the server response with this header:
Date
is the time of downloading andlast-modified
seems to change every 30 minutes. It would be best, if this information were available in the header sent by the server. Of perhaps in a separate text/json file on the server.The text was updated successfully, but these errors were encountered: