OpenStreetMap 标志 OpenStreetMap

电子邮件图标 Bluesky图标 Facebook图标 LinkedIn图标 Mastodon图标 Telegram图标 X图标

讨论

amm2009年11月 5日 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.

Firefishy2009年11月 9日 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.

登录以留下评论