We are please to announce a new version of all our modules which brings new features and improves stability:

• Apache / Nginx / Varnish: DataDome modules can now inject bot information in headers that can be used in your application or add in webserver logs
• Apache: Disable/Enable DataDome module at Virtualhost Level or htaccess
  https://docs.datadome.co/docs/apache#section-can-i-disable-the-module-for-specified-location-or-query-params-

All our users are invited to upgrade the module to enjoy these new functionalities!

Apache v2.33 (2017-03-16)

• Implemented support X-DataDome-request-Headers
• Renamed configuration options to DomeName
• Fixed issue when module's configuration is specified inside virtual host
• Added support DATA_DOME_DISABLE environment variable to temporary disable the module
• Allow specified Module's directives at any place in the config

Nginx v2.31 (2017-03-24)

• Reduce traffic size between module and APIServer
• Added compatibility with nginx before 1.5.8, 1.5.6 and 1.5.3
• Removed warnings for nginx before 1.9.11
• Implemented support X-DataDome-request-Headers

Varnish v2.26 (2017-03-16)

• Implemented support X-DataDome-request-Headers
• Reset memory that is used as new headers for the API server call
• Synced version with another varnish versions

We are today releasing the 2.1 version of the dashboard!

New design, new features, let's review it all:

• added possibility to view last hits from each bot IP (by clicking on an IP on the dashboard)
• three new features are enabled in configuration view:
  • invite users to your dashboard using the user system
  • enable/disable general blocking (premium only)
  • segments list on your account

We are proud to release the new Varnish version which contains a few improvements to improve performance.

v2.24 (2017-01-25)

• Removed X-DataDome headers at real backend request and introduced data_dome_shield.cleanup_backends_request
• Don't copy URI for regex matching
• Moved from syslog to standard varnish logging way

We are proud to release the new ASP.NET version which contains a many improvements, including compatibility with .NET 3.5.

Access to the doc

v2.2 (2017-01-04)

• Added verification by X-DatadomeResponse response header.
• Sent request's headers name to the API server.
• Sent request's Connection header value to the API server.
• Sent request's Pragma header value to the API server.
• Sent request's Cache-Control header value to the API server.
• Sent request's Method header value to the API server.
• Sent request's X-Requested-With header value to the API server.
• Sent request's Origin header value to the API server.
• Send Cookies length to the API server.
• Send Cookies Body length to the API server.
• Send Authorization length to the API server.
• Compatible with .NET Framework 3.5 or older.
• Disable send Cookies to API server.
• Disable send Body to API server.
• Module don't generate ClientID.
• Support X-DataDome-headers from API response.
• Fixed ignored proxy configuration in the web.config file.

We are pleased to release a brand new version of our Varnish, Apache & Nginx modules.

Don't hesitate to upgrade your DataDome modules to enjoy our last detection improvements !

DataDome can be used with any major CDN. The module is able to identify the real client IP that actually requests the page, and considers all IP ranges used by CDN service providers as Trusted Proxy.

Depending on your CDN, some configuration may be required.

The default Akamai configuration works seamlessly with the DataDome module, as it forwards all required information to the Origin.

If you are using Amazon CloudFront, on the other hand, you need to configure it to forward required information to the Origin.

Integrate your CDN with DataDome
In terms of cache management, DataDome will protect all hits that reach the Origin. If you need to protect all your content, we recommend the usage of a specific header to force the CDN to reach the Origin for each hit. This will not disable the cache, but forces the CDN to check cache validity for each hit. The packet is very light (no content), and resulting overhead will be very limited.

If you are using a single or a multi-CDN architecture, please check our new documentation Integrate your CDN with DataDome

The DataDome technology is deployed in multiple regions, in order to optimize latency between your servers and our API Servers. We are currently using four data centers, in Ireland, Germany, France and the USA (Virginia), respectively.

You can now check the status of the DataDome API servers in real time!

We have set up a web page showing the status of all our servers in real time. From the main page, you can click through to each individual data center for additional details.

You can find the status page here: http://status.datadome.co.

If you notice any anomalies in how the DataDome module is behaving, consider checking this page to determine if we are having server issues (in which case we will already be working on them).

We are proud to release the new Apache version which contains a few improvements and a new log feature.

Get more information in the Changelog Apache

v2.26 (2016-11-10)

• Improved compatibility with HAProxy
• Added DATA_DOME_STATUS and DATA_DOME_SPENT_TIME envirnoment variable
• Added 7xx status code to provide internal module status
• Removed compilation warning
• Improved timeout
• Picked up random resolved address

DataDome technology is deployed in several regions to provide the best latency between your servers and our API Servers.

After the deployment in three AWS DataCenters (Irland, Germany and Virginia, USA), we are proud to announce that a fourth region has been added in France (Paris), at Online.

You can use our latency script to check performance between your servers and this new region. All endpoints are available in the API Server documentation .

We are happy to see some users' latency going from 20ms to 7ms.