Changelog

We've added the ability to define negated rules by prefixing the filter with a dash ("-"). This allows you to dive into your analytical overview deeper by excluding some traffic.

Example: `-country:US`

We've expanded the Analytics support article for more info. Read more.

You can now create infinite complex redirect rules by utilizing a regex matching for your path based redirects. Use the capture group results in the destination to pass along specific path elements from the incoming URL. This powerful feature is now available for our users in the Pro plan and up.

Read more

We've added the following API endpoints:

- GET /api/v1/domains
- GET /api/v1/domains/{id}
- POST /api/v1/domains/{id}/check-dns

The `check-dns` endpoint can be handy to force-check a specific domain after the DNS changes have been made with your DNS provider.

Our documentation and PHP SDK are updated as well.

When users have been using password based authentication and SAML2 is activated, users have the ability to either use SAML2 or their original password authentication. This can be useful for the primary team owner, which should be able to fallback to password based authentication in case of a SAML failure.

We've added the ability to disable password authentication for other team members by the owner. This ensures that existing team members before being added with SAML SSO, can have their original password disabled. This strengthens the SAML SSO flow, as it's the only way for authentication.

Happy to announce that we now have support to select the HTTP verb/method in the destination monitor. 

We use HEAD requests for our destination monitoring tool. As some providers might be blocking HEAD requests, we added the ability to specify the HTTP verb. We've added POST/PATCH/PUT support as well.

When a destination returns a 405 status code ('Method not allowed'), we automatically switch to GET requests.

To provide a better overview of your redirects, we now show the path fowarding & query string forwarding setting of the redirect in the overview, so that you can quickly see where it is enabled or disabled. 

• We've added 'path' in the destination when path forwarding is enabled
• We've added 'query' in the destination when query string forwarding is enabled.

To better indicate our redirect settings to the general public, we have changed the names of the following two settings:

• Renamed "URI forwarding" to "Path forwarding"
• Renamed "Keep query string" to "Query string forwarding"

By popular demand, we've worked on providing a Terraform Provider to allow managing your redirects easily in your IaaC. We're happy to announce public availability of this provider with an official listing on the Terraform Registry.

Do you have any improvements to make this provider even better? Pull requests are more then welcome.