Closed giorgi1324 closed 1 month ago
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (http
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
http documentation http source (message by IssueLinks)
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
As in title - failed login attempts return 200 while they should return 401. This circumvents
nginx
/fail2ban
setup that I rely on for basic abuse prevention:What version of Home Assistant Core has the issue?
core-2024.6.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
Not relevant
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response