Many web application firewalls notably those that incorporate modsecurity block *.conf files. This breaks Bluemap as it uses .conf files for localisation.

Would it be possible to use a different file extension so that it keeps the firewalls happy?

@Hackatrons
BlueMap uses HOCON for its localisation files (as with all of its config files) to make them as easy as possible to read and edit.
And hocon files have the .conf ending. Changing that would mean that we also need to change the entire localisation language to not create some really weird mess with having hocon with a non-standard file-ending.

This is the first time I hear about this issue, so i am not so sure about the "many" part ^^
I would consider this if this would be an obvious problem for a lot of people, but right now it just seems to be a very specific problem with your setup. So for now I think this should be solved on your end. :)

Also, as noted in our contributing guidelines, suggestions should go in our discord channel where i can keep track of them much better. GitHub issues are for bugs and planned features only :)

Does whatever firewall you're using that's doing this not support being customised so that it will allow the .conf files?

Unfortunately no, it doesn't offer that level of granularity.
Currently I have the entire firewall disabled for Bluemap, but it would be nice if it could run behind it.