Now try to login, sync etc… and see what requests are sent and received. This will open a new window where you will see the output, errors, network traffic etc… from the bitwarden extension. Right-click somewhere in the bitwarden pop-up and click on Inspect Element.Then open the Bitwarden Extension by clicking on the icon.Enable the Show Develop menu in menu bar option under the Advanced settings of Safari.It would be nice if someone could test the Bitwarden Plugin in Safari using the Developer Console to see what happens. I have tested the patch also, it does also work, but i’m not seeing any difference in the plugin in Safari. Thus it could be that the reverse proxy is doing something which removes or changes these headers? Since bitwarden_rs already returns ‘*’ as the allowed CORS instead of the specific requested file://.
I have tested it with and without these changes using the latest Bitwarden version, but i’m not having issues.