[OSM-dev] Improvement of tile rendering
D Tucny
d at tucny.com
Wed Mar 18 02:58:48 GMT 2009
2009/3/18 Stefan de Konink <stefan at konink.de>
> Jon Burgess wrote:
> > On Wed, 2009-03-18 at 00:48 +0100, Stefan de Konink wrote:
> >> Dane Springmeyer wrote:
> >>> I should stress though that Mod_tile is the optimal solution for tile
> >>> rendering for most OSM related purposes.
> >> I wonder if an Apache module is able to provide caching. I doubt it can,
> >> thus requires more bandwidth right?
> >
> > Yes it does caching. What make you think it can not?
>
> I am talking about client side caching. So a client says... hey I have
> an expire thingie or i have an e-tag should I refetch it?
>
Here are the headers for a request and response for a single tile...
GET /16/54640/26982.png HTTP/1.1
Host: b.tile.openstreetmap.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.7)
Gecko/2009021910 Firefox/3.0.7
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en,en-gb;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://www.informationfreeway.org/
HTTP/1.x 200 OK
Date: Wed, 18 Mar 2009 02:54:03 GMT
Server: Apache/2.2.4 (Ubuntu)
Etag: "b3431afd380b6449ac17e631eef4536d"
Content-Length: 5338
Cache-Control: max-age=8987
Expires: Wed, 18 Mar 2009 05:23:50 GMT
Keep-Alive: timeout=3, max=100
Connection: Keep-Alive
Content-Type: image/png
So, it returns an Etag header, a cache-control header giving an approx 2.5hr
max-age and an Expires header also giving the same 2.5hr age... Looks good
to me :)
d
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20090318/0290d951/attachment.html>
More information about the dev
mailing list