Please check if the PR fulfills these requirements
[X] The branch naming convention follows our guidelines
[X] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fix Unauthorized error when logging in qBitTorrent WEB GUI using Firefox or other affected browsers.
Cause is referenced here.
What is the current behavior? (You can also link to an open issue here)
When setting non default credentials and using Firefox as browser (others may be affected too), we face an Unauthorized error after login.
What is the new behavior (if this is a feature change)?
If the error occurs, simply set the flag qbittorrent.csrf_protection to false and redeploy (no upgrade supported so far).
In this way, users should be able to login on the WebGUI.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No braking change, since the default settings (if users do not update their own value file) will disable CSRF Protection by default.
Please check if the PR fulfills these requirements
[X] The branch naming convention follows our guidelines
[X] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fix Unauthorized error when logging in qBitTorrent WEB GUI using Firefox or other affected browsers. Cause is referenced here.
What is the current behavior? (You can also link to an open issue here) When setting non default credentials and using Firefox as browser (others may be affected too), we face an
Unauthorizederror after login.What is the new behavior (if this is a feature change)?
If the error occurs, simply set the flag
qbittorrent.csrf_protectionto false and redeploy (no upgrade supported so far). In this way, users should be able to login on the WebGUI.No braking change, since the default settings (if users do not update their own value file) will disable CSRF Protection by default.
Closes #27