You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you scroll down the icons for the sites will start to fill
My DNS server reports:
RATE_LIMIT | Client 192.168.30.221 has been rate-limited (current config allows up to 1000 queries in 60 seconds)
After the site icons stop filling and have a generic placeholder
Expected Result
I would expect that the ICON files should be cached locally not looked up when the Bitwarden container is started, and a client connects.
Actual Result
I would expect the ICONs to cache and be presented to the client vs a large block of DNS lookups to go to the site and pull the ICONs. There could be a Time to Live to refresh ICON's to keep them up to date.
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
RATE_LIMIT | Client 192.168.30.221 has been rate-limited (current config allows up to 1000 queries in 60 seconds)
Expected Result
I would expect that the ICON files should be cached locally not looked up when the Bitwarden container is started, and a client connects.
Actual Result
I would expect the ICONs to cache and be presented to the client vs a large block of DNS lookups to go to the site and pull the ICONs. There could be a Time to Live to refresh ICON's to keep them up to date.
Screenshots or Videos
No response
Additional Context
No response
Githash Version
2023.7.2
Environment Details
Server:
Operating System: Proxmox LXC container running Debian 12
Docker version 24.0.5, build ced0996
Client:
Windows 10 Pro Desktop Client
Version 2023.7.1
Shell 24.1.1
Renderer 112.0.5615.50
Node 18.14.0
Architecture x64
Database Image
image: mariadb:10
Issue-Link
#2480
Issue Tracking Info
The text was updated successfully, but these errors were encountered: