v3.11.7

• Introduced more granular errors for proxy integration failures and request filtering
• Increased Smart Signals accuracy

More granular errors

Introduced more granular error constants for network request filtering and proxy integration failures:

• FingerprintJS.ERROR_NETWORK_RESTRICTED triggered when a request is filtered out based on an IP address or IP address range
• FingerprintJS.ERROR_INVALID_PROXY_INTEGRATION_SECRET occurs when the Fpjs-Proxy-Secret header contains an empty, invalid, or non-matching value
• FingerprintJS.ERROR_INVALID_PROXY_INTEGRATION_HEADERS triggered when the proxy integration headers are misconfigured or partially provided in those specific cases:
  • Missing required headers (Fpjs-Proxy-Client-IP, Fpjs-Proxy-Forwarded-Host).
  • Duplicate headers
  • Invalid patterns for Client-IP or Forwarded-Host

Note: We're awaiting the backend implementation for FingerprintJS.ERROR_INVALID_PROXY_INTEGRATION_SECRET and FingerprintJS.ERROR_INVALID_PROXY_INTEGRATION_HEADERS but you can preemptively use them to troubleshoot your integration when they become fully available.

Smart Signals accuracy

Significantly improved the accuracy of the Virtual Machine Detection Smart Signal.