[OSM-dev] CORS headers on OSM tiles (for WebGL use)
Jaak Laineste
jaak.laineste at gmail.com
Sun Sep 18 19:18:16 BST 2011
2011/9/17 klokan at gmail.com <klokan at gmail.com>:
> Dear OSM developers,
>
> Would it be possible to add the CORS HTTP header: Access-Control-Allow-Origin: *
> to the OSM tileserver when a tile is requested?
>
> It will officially allow to use the OSM tiles as WebGL textures and
> Canvas source in web browser - both in 3D globes and 2D applications
> (color adjustments, etc).
Have you considered other options, especially setting up own
tileserver with all your needed configurations? AFAIK the OSM main
tileserver (bandwidth) is quite busy, it has the main job to do as
"preview OSM database map" in openstreetmap.org. So other applications
(especially of bulk download type) are not really that welcome there.
Also there can occasions when the tileserver is taken down for
maintenance.
If you have low load and no availability requirements, and setting up
own tileserver is too much (it really takes 30 minutes or so) then you
can also set up own tilecache/proxy (with all your headers) and use
osm tileserver only for cache misses.
--
Jaak
More information about the dev
mailing list