nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Refferer-Policy Headers

DarrenAD23

Hi,

This is my first time on the forum and was wondering if anyone able to provide a solution for the error message that i have recently started to receive whilst using OpenStreetMap (OSM). The issue "Access Blocked 403r" appears to be connected to their "Refferer-Policy". Details from the openstreetmaps.org/wiki/Blocked-Titles states the following……

If the tile mentions "Referer is required" then you were automatically blocked because your application/website is not sending HTTP Referer headers, but doing so is required by the tile usage policy. This block will resolve itself once you make the necessary changes to your application, without further intervention necessary.

For websites/web applications, this can be fixed by setting your Referrer-Policy header to any of no-referrer-when-downgrade, origin, origin-when-cross-origin, strict-origin, or strict-origin-when-cross-origin.

Therefore is there a setting that I need to amend or allow within Bitdefender that will send the appropriate Refferer Headers?