The fix would be to change HIFIS.Web/Web.config to use “strict-origin-when-cross-origin” instead of “strict-origin”.
Please note that this issue has been addressed and a permanent fix will be included in HIFIS version 61.3, which is scheduled for release in November 2026.
@Ryan Booker proposes fixing the issue by changing <add name="Referrer-Policy" value="strict-origin"/> to <add name="Referrer-Policy" value="same-origin"/>
This tag is found in web.config under <httpProtocol><customHeaders>
Official reply:
The fix would be to change HIFIS.Web/Web.config to use “strict-origin-when-cross-origin” instead of “strict-origin”.
Please note that this issue has been addressed and a permanent fix will be included in HIFIS version 61.3, which is scheduled for release in November 2026.
@Ryan Booker proposes fixing the issue by changing
<add name="Referrer-Policy" value="strict-origin"/>to
<add name="Referrer-Policy" value="same-origin"/>This tag is found in web.config under
<httpProtocol><customHeaders>