Thread Starter
Lap
(@lapzor)
Fixed it, needed to add
add_header Referrer-Policy “strict-origin-when-cross-origin” always;
in my vhost
Hi Lap @lapzor,
Thanks for reporting the issue, and great to hear you got it sorted out!
Your solution will be helpful for others who may run into the same error, so I really appreciate you sharing it.
Thanks, Phi.
Thread Starter
Lap
(@lapzor)
Note for other users:
of course the way how to set the referrer-Policy depends on your server, in my case it’s ngnix and i have access to my vhost file so I did it there.
On other servers you might do it via htaccess or maybe the easiest way by adding a meta tag to your wordpress
htaccess version:
<IfModule mod_headers.c>
Header set Referrer-Policy "strict-origin-when-cross-origin"
</IfModule>
or meta tag (in your <head>
<meta name="referrer" content="strict-origin-when-cross-origin">