Makes a HEAD request to find out the latest modification date as reported by the HTTP headers from S3. This should at least partially address issue #6.
A similar approach could also be used to dynamically fetch and display the actual file size of the planet (and country extracts, see #7) files – instead of having a hardcoded file size (which is quickly outdated: now it shows 24.3 GB while the actual file is mor like 33.7 GB large). But for that to work the osm-qa-tiles would need to allow a CORS site to read the Content-Length header (by setting the Access-Control-Expose-Headers = Content-Lenght header in the response). //cc @geohacker: Can you guys set that up on the S3 bucket? If yes, I can include that in this PR as well.
Makes a
HEAD
request to find out the latest modification date as reported by the HTTP headers from S3. This should at least partially address issue #6.A similar approach could also be used to dynamically fetch and display the actual file size of the planet (and country extracts, see #7) files – instead of having a hardcoded file size (which is quickly outdated: now it shows
24.3 GB
while the actual file is mor like33.7 GB
large). But for that to work the osm-qa-tiles would need to allow a CORS site to read theContent-Length
header (by setting theAccess-Control-Expose-Headers = Content-Lenght
header in the response). //cc @geohacker: Can you guys set that up on the S3 bucket? If yes, I can include that in this PR as well.