Logo de OpenStreetMap OpenStreetMap

Ícono de correo electrónico Icono de Bluesky Ícono de Facebook Ícono de LinkedIn Ícono de Mastodon Ícono de Telegram Ícono X

Discusión

Comentario de amm el 5 de noviembre de 2009 a las 20:24

1) As far as I know, the reason for dropping the last-modified header and replacing it with an etag derived from the md5 of the actual tile, is that the last-modified will change more often than the actual content of the tile. As the tile expiry and (meta) tile rendering over estimates the number of tiles that need to be rerender after a change in the data, many tiles get rerendered to the same content. If the cache expiry were based on the modified time instead, it would reduce the caching efficiency.

2) The dev mailing list is probably the best place to discuss this.

Comentario de Firefishy el 9 de noviembre de 2009 a las 10:18

If I recall last-modified was dropped because apache uses an AND (as per RFC) on subsequent requests supplied with etag and if-modified-since, which was causing much lower hit ratio.

Iniciar sesión para dejar un comentario