Add Google S2 icon cache fallback for favicon fetching#6881
Add Google S2 icon cache fallback for favicon fetching#6881Shocker wants to merge 1 commit intodani-garcia:mainfrom
Conversation
|
I'm not in favor of this. If you want to use Google, DuckDuckGo or even Bitwarden's version, you can already configure this. So, from my point of view this is not going to be implemented. |
I apologize for not knowing about the ICON_SERVICE. I mostly agree with what you said. Then what about adding an extra config to have ICON_SERVICE act as a fallback to the internal downloader instead of replacing it completely, and have it work only when the internal downloader fails? |
|
I already tried to add some missing favicons by hand but Vaultwarden manages the directory and would just delete them after a while. Might make sense to have a user managed fallback favicon directory for that? |
Have you read the wiki article that explains how to use custom icons? It has a section about cache expiration and explains how to prevent your custom placed items from getting deleted. |
|
I am proposing #6882 instead |
LATER EDIT: ignore the request but see the comments below
In case the favicon download fails due to anti-bot/anti-crawler techniques (most likely HTTP code 403 or even 444) fallback to Google icon cache which is almost sure to have the favicon cached.
While it may seem a bad idea to hardcode links like this, an increasingly amount of sites started using such techniques, especially aggressive Cloudflare-protected sites, causing Vaultwarden to fail in fetching favicons
P.S.: For this pull request to work, #6880 also needs to be accepted/merged