mirror/aliasvault
1
0
Fork 0
mirror of https://github.com/aliasvault/aliasvault.git synced 2026-08-02 18:28:49 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update FaviconExtractor headers to improve success rate

Browse Source
This commit is contained in:
Leendert de Borst
2026-08-02 22:57:49 +02:00
parent 86a7bca474
commit 9adfb62bae
1 changed files with 12 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
apps/server/Utilities/AliasVault.FaviconExtractor/FaviconExtractor.cs
View File

@@ -526,7 +526,8 @@ public static class FaviconExtractor
};
// Use random User-Agent
client.DefaultRequestHeaders.Add("User-Agent", userAgents[random.Next(userAgents.Length)]);
var userAgent = userAgents[random.Next(userAgents.Length)];
client.DefaultRequestHeaders.Add("User-Agent", userAgent);
// More comprehensive Accept header with image types prioritized
client.DefaultRequestHeaders.Add(
@@ -540,17 +541,17 @@ public static class FaviconExtractor
client.DefaultRequestHeaders.Add("Upgrade-Insecure-Requests", "1");
client.DefaultRequestHeaders.Add("Cache-Control", "max-age=0");
// Add Sec-Fetch headers to mimic modern browsers
if (random.Next(2) == 0)
{
client.DefaultRequestHeaders.Add("Sec-Fetch-Dest", "document");
client.DefaultRequestHeaders.Add("Sec-Fetch-Mode", "navigate");
client.DefaultRequestHeaders.Add("Sec-Fetch-Site", "none");
client.DefaultRequestHeaders.Add("Sec-Fetch-User", "?1");
}
// Sec-Fetch headers to mimic modern browsers. Every real browser sends these on a top-level
// navigation, and some sites (facebook.com among them) answer a request without them with an
// HTTP 400, so they are always sent rather than randomly.
client.DefaultRequestHeaders.Add("Sec-Fetch-Dest", "document");
client.DefaultRequestHeaders.Add("Sec-Fetch-Mode", "navigate");
client.DefaultRequestHeaders.Add("Sec-Fetch-Site", "none");
client.DefaultRequestHeaders.Add("Sec-Fetch-User", "?1");
// Add Chrome-specific headers randomly
if (random.Next(3) == 0)
// Chrome client hints, but only when the picked User-Agent is actually Chrome: announcing Chrome
// hints alongside the Firefox User-Agent is exactly the mismatch bot protection screens for.
if (userAgent.Contains("Chrome", StringComparison.Ordinal))
{
client.DefaultRequestHeaders.Add("Sec-CH-UA", "\"Not_A Brand\";v=\"8\", \"Chromium\";v=\"120\", \"Google Chrome\";v=\"120\"");
client.DefaultRequestHeaders.Add("Sec-CH-UA-Mobile", "?0");