mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Wrong favicons for ports and subdomains #1657
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rakuri255 on GitHub (Aug 5, 2023).
Wrong favicons for ports and subdomains
If you have applications with own favicons, which are in host:port or in subdomain.domain, only host:80 and domain will be used. So you always have the wrong favicons. But it works when you create a new entry for a subdomain.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
vaultwarden version: 1.29.1
Install method: Docker image
Clients used: web vault, desktop, Android, iOS
Steps to reproduce
Create some webpages with different favicons
Web 1: http://192.168.0.218:80 -> Favicon 1
Web 2: http://192.168.0.218:8888 -> Favicon 2
Web 3: http://192.168.0.218:9999 --> Favicon 3
Web 1: https://mainDomain.com -> Favicon 1
Web 2: https://subDomainOne.mainDomain.com -> Favicon 2
Web 3: https://subDomainTwo.mainDomain.com--> Favicon 3
Empty the server icon cache, after saving all entry to vaultwarden.
Expected behaviour
Should have a different favicon for each host:port and for each subdomain
Actual behaviour
Shows only the icon from the host
Web 1: http://192.168.0.218:80 -> Favicon 1
Web 2: http://192.168.0.218:8888 -> Favicon 1
Web 3: http://192.168.0.218:9999 --> Favicon 1
Web 1: https://mainDomain.com -> Favicon 1
Web 2: https://subDomainOne.mainDomain.com -> Favicon 1
Web 3: https://subDomainTwo.mainDomain.com--> Favicon 1
Troubleshooting data
It works when you create a new entry for a subdomain.
But it dont works when the icon cache is empty and need to redownload the favicon.
@BlackDex commented on GitHub (Aug 5, 2023):
Ports do not work, those are not passed by the clients, so nothing we can do there.
If the subdomains do not provide a website, or need login or do not have any valid
<link>tags for the icons it will try the main domain.You could enable debug log_level which should provide some info onto why it gets skipped, just make sure you cleared the cache before doing the test, else it will skip it.