OpenStreetMap 로고 OpenStreetMap

이메일 아이콘 Bluesky 아이콘 Facebook 아이콘 LinkedIn 아이콘 마스토돈 아이콘 텔레그램 아이콘 X 아이콘

토론

2009년 11월 5일 20:24amm님의 의견

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.

2009년 11월 9일 10:18Firefishy님의 의견

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.

댓글을 남기려면 로그인하세요