Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
PR #4645 introduced CSRF checks into the web interface. When a POST request is submitted to "save" a config change, there is no visual indication presented to the user that the request has failed.
Additionally, nothing is logged to the server-side log, even with verbose logging enabled.
Users must retry the web request with developer tools open, and review the logs for a 400 error that contains the detailed error message.
Expected Behavior
An error message (HTML or even browser window alert) should be presented to the user, especially since a "success" message is normally presented. Ideally this would contain the API error message, but even something more generic like "HTTP 400 error when submitting changes" would be helpful.
Additional Context
No response
Host Operating System
Linux
Operating System Version
Fedora 43
Architecture
amd64/x86_64
Package
Linux - Fedora Copr
GPU Type
AMD
GPU Model
N/A
GPU Driver/Mesa Version
N/A
Capture Method
None
Apps
Log output
Online logs
No response
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
PR #4645 introduced CSRF checks into the web interface. When a POST request is submitted to "save" a config change, there is no visual indication presented to the user that the request has failed.
Additionally, nothing is logged to the server-side log, even with verbose logging enabled.
Users must retry the web request with developer tools open, and review the logs for a 400 error that contains the detailed error message.
Expected Behavior
An error message (HTML or even browser window alert) should be presented to the user, especially since a "success" message is normally presented. Ideally this would contain the API error message, but even something more generic like "HTTP 400 error when submitting changes" would be helpful.
Additional Context
No response
Host Operating System
Linux
Operating System Version
Fedora 43
Architecture
amd64/x86_64
Package
Linux - Fedora Copr
GPU Type
AMD
GPU Model
N/A
GPU Driver/Mesa Version
N/A
Capture Method
None
Apps
Log output
Online logs
No response