[Tile-serving] [openstreetmap/mod_tile] Missing CORS in renderd.conf and 403 HTTP errors returned by mod_tile (Issue #499)

[Christian Quest]

cquest created an issue (openstreetmap/mod_tile#499)

The current code taking care of CORS return 403 errors when the Origin header in the client request does not match the CORS=xxx parameter in renderd.conf or when it is missing.

It does not seem logical as CORS is to be handled by the client, not by the server.

It could be seen as a way to limit access to the tileserver but in fact, this test is done by mod_tile AFTER calling renderd and generating the metatile.

I don't really understand the logic, that why I have no PR to offer so far.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/mod_tile/issues/499
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/mod_tile/issues/499 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20260618/a7dbf41c/attachment.htm>