Skip to content

Add Google S2 icon cache fallback for favicon fetching#6881

Closed
Shocker wants to merge 1 commit intodani-garcia:mainfrom
Shocker:google-s2-fallback
Closed

Add Google S2 icon cache fallback for favicon fetching#6881
Shocker wants to merge 1 commit intodani-garcia:mainfrom
Shocker:google-s2-fallback

Conversation

@Shocker
Copy link
Copy Markdown
Contributor

@Shocker Shocker commented Feb 27, 2026

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

@BlackDex
Copy link
Copy Markdown
Collaborator

I'm not in favor of this.
The whole reason to have a self-working favicon downloader is to not use external sites like Google or any other favicon provider.

If you want to use Google, DuckDuckGo or even Bitwarden's version, you can already configure this.
Most people do not want companies like Google or which ever to track these kind of items.

So, from my point of view this is not going to be implemented.

@Shocker
Copy link
Copy Markdown
Contributor Author

Shocker commented Feb 27, 2026

I'm not in favor of this. The whole reason to have a self-working favicon downloader is to not use external sites like Google or any other favicon provider.

If you want to use Google, DuckDuckGo or even Bitwarden's version, you can already configure this. Most people do not want companies like Google or which ever to track these kind of items.

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?

@larena1
Copy link
Copy Markdown

larena1 commented Feb 27, 2026

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?

@stefan0xC
Copy link
Copy Markdown
Contributor

I already tried to add some missing favicons by hand but Vaultwarden manages the directory and would just delete them after a while.

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.

@Shocker
Copy link
Copy Markdown
Contributor Author

Shocker commented Feb 27, 2026

I am proposing #6882 instead

@Shocker Shocker closed this Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants