|
Hi to all, I want to setup an own OSM Tile server for integration into my application. But I'm a little concerned that it's very easy to cause the OSM tile server to fail with a denial of service attack on the URL-instructions ...123.png/dirty or /statusinfo. Now, of course, I could put an NGNX in front and filter out the URL-instructions via regex. Nevertheless I would like to ask here in the round whether the server has perhaps a simple option to disable these URL instructions? I thank you in advance... |
|
A typical tile server configuration would include something like to disallow the "dirty" and "status" requests. (Replace "tiles" with whatever your tile URL is.) You could do the same with mod_tile's status request (/mod_tile) although this is not expensive to serve, it is just information that you might not want to publish. If you're using something that monitors your tile server, e.g. munin, you would not outright disallow /mod_tile but do something like |
|
Firstly, it's just Apache. Any filtering, throttling or other restrictions that work with Apache elsewhere will also work here. Secondly, mod_tile supports throttling - see https://github.com/openstreetmap/mod_tile/search?q=throttling . If you change anything from the defaults you'll want to make sure that "normal" actions like just browsing around the map aren't throttled too. |
