You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it somehow possible to restrict the access to the tileserver to certain websites so not anybody is able to use the tileserver on other websites? I searched a lot but couldn't find a hint that tessera/tilelive are capable of that. Of course I could install something like iptables and block traffic by referrer etc. but I hope there is a solution that can easily be configured.
There seems to be the possibility to configure domains in /project/config.json (docker run -d -v $(pwd):/data -e DOMAINS='www.example.com' -p 80:80 klokantech/tileserver-mapnik) but it seems like this has nothing to do with restricting access. What is it good for? Couldn't find anything in the tessera documentation.
P.S. I know, to realize such a simple access restriction the server has to rely on data from a client and this data can be spoofed/manipulated. But it would at least give some security.
The text was updated successfully, but these errors were encountered:
Is it somehow possible to restrict the access to the tileserver to certain websites so not anybody is able to use the tileserver on other websites? I searched a lot but couldn't find a hint that tessera/tilelive are capable of that. Of course I could install something like iptables and block traffic by referrer etc. but I hope there is a solution that can easily be configured.
There seems to be the possibility to configure domains in /project/config.json (docker run -d -v $(pwd):/data -e DOMAINS='www.example.com' -p 80:80 klokantech/tileserver-mapnik) but it seems like this has nothing to do with restricting access. What is it good for? Couldn't find anything in the tessera documentation.
P.S. I know, to realize such a simple access restriction the server has to rely on data from a client and this data can be spoofed/manipulated. But it would at least give some security.
The text was updated successfully, but these errors were encountered: