February 12th, 2025
Remove "Error" message from verbose console logs
February 4th, 2025
January 29th, 2025
Add new options:
DATADOME_TENANT_NAME: identify instances in a multi-tenancy environment on EnvoyDATADOME_ENABLE_UNPROTECTED_CACHED_RESPONSE: omit Set-Cookie and enriched headers from allowed responses that can be cachedDATADOME_CLUSTER_NAME: define a name for the cluster that will connect to DataDome
Expose status code of Protection API responses as X-DataDome-status in enriched headers
Add enriched headers to the headers of challenged requests
Match inclusion and exclusion patterns with the host and path of request URLs (previously only matched the path)
January 27th, 2025
Add support of CIDR notation in DATADOME_IP_FILTERING
Remove unused code related to deprecated App
January 21st, 2025
Rename configuration parameter for GraphQL support to datadome_enable_graphql_support for consistency
Clean payload sent to Bot Protect API to remove fields with empty value
January 20th, 2025
Change requests to Protection API to get 200 status codes on block responses and avoid closing connections on 403 responses, optimizing connection time for overall traffic
Increase BUFFER_RECEIVE to extend the TCP window length and avoid potential reconnections when certificate is too big
Set default timeout to 150ms
January 16th, 2025
Restore the original referrer value on document.referrer after a navigation request is challenged
Hide Device Check when using invisible mode to prevent visual glitches
January 16th, 2025
Update list of allowed endpoint_type for adding , updating , and importing custom rule resources
January 15th, 2025
Display challenges for XMLHttpRequest requests using arraybuffer response type
Internal optimizations
January 9th, 2025
