map Access blocked 403r on memories

[soliloquies]

Describe the bug

Access blocked

Referer is required by tile usage policy of OpenStreetMap's volunteer-run servers: osm.wiki/Blocked

Steps To Reproduce

No response

Platform

- OS:
- Browser:
- Memories Version:
- Nextcloud Version:
- PHP Version:

Screenshots

No response

Additional context

• Any errors in the JS console?
• Any errors in the Nextcloud server logs?

[ShinjiLE]

[cmossde]

Same here on all nextcloud instances (32.0.6 and 33.0.0) and even on the demo-server of this project.

I'm using the docker community image behind traefik 3. Tried to set the referer via traefik with the URL of the instance, but that didn't help.

Seem OSM blocked certain applications. Is memories one of them?

[soliloquies]

This only occurs in memories, which may be the only one using OpenStreetMap's map service?

[pfl]

I can confirms Memories (and Nexcloud maps) are both showing the blocked banner with their default setup. I have a small server just for myself so the banner is not a result of massive traffic. Is the Referer header something that can be enabled from Apache web server, or does it need to be set by Memories when downloading tiles?

[soliloquies]

That should be resolved now. I updated the nginx header configuration to change the referrer policy from no-referrer to strict-origin. I'll monitor it over the next few days and follow up with feedback

#        add_header Referrer-Policy                   "no-referrer"       always;
        add_header Referrer-Policy                   "strict-origin"      always;

[pfl]

In the nextcloud installation directory there is the .htaccess file, which always unsets Referrer-Policy header in the server and then sets it to "no-referrer". My quick fix was to change the else block to "strict-origin"

    <Else>
      Header onsuccess unset Referrer-Policy
      Header always set Referrer-Policy "strict-origin"
    </Else>

Not sure this was the intended way to fix this, but at least I got rid of the access blocked tiles due to missing referer header.

[soliloquies]

it had to adjust the nginx Referrer-Policy configuration be solve this situation for my self-host server.