Open oldwired opened 2 years ago
Hi, is your Nominatim instance still served by Apache behind your reverse proxy?
I encountered a similar issue today and solved it by adding AddType application/json .php
to the Apache config.
It seems to be an issue noted in the Nominatim Docker repo already https://github.com/mediagis/nominatim-docker/issues/133
I encountered a similar issue today and solved it by adding
AddType application/json .php
to the Apache config.
Thanks, works for me. :)
Unfortunately not work for me. The same error 406.
@rooton have you checked the issue https://github.com/mediagis/nominatim-docker/issues/133 ? Looks like it's a problem with the nominatim-docker package
@oldwired Yes, thats definitely issue with nominatim-docker package. Firstly I have added AddType application/json .php
on top of AddType text/html .php
and it didn't work, but after moving application/json under text/html it finally worked.
@oldwired Yes, thats definitely issue with nominatim-docker package. Firstly I have added
AddType application/json .php
on top ofAddType text/html .php
and it didn't work, but after moving application/json under text/html it finally worked.
hi where you add these line can you explain to me
When trying to use the plugin with my own instance of nominatim (behind a caddy reverse proxy), which works via browser address bar and Postman, I get the following errors:
My code:
General:
Response Headers:
Request Headers:
Like I mentioned, I use a caddy reverse proxy, but that should not matter, because the it also doesn't work if I use a direct connection. If I let caddy add an
Access-Control-Allow-Origin *
header I still get the 406 (but not the CORS violation). But when I try postman or the browser access bar for a direct get to the nominatim API the header is already present, so that can't be the problem.