Changelog

When importing (any number of) redirects, it could create cases where the edge refreshing queue becomes full, as the entire team's portfolio of domains would be refreshed.

We've rewritten these code paths to ensure we only refresh domains on the edge that have been changed. This ensures that when importing domains, newly made changes are propagated quickly. 

This didn't effect API or UI usage.

We've added support for regex capture groups to be used in the dynamic destination expression language. For instance, you can now check regex results with expressions like `$1 == 'a-path-to-check'`

We've reworked our API code paths to prevent overlapping race conditions if a multitude of changes on the same domain name were made in quick succession. We now ensure only a singular action per domain name is executed via locking.

redirect.pizza provides an ultra-stable edge network. Even though we have never had a global outage, we continuously work to ensure the most stable platform.

We've launched another set of edge nodes, separate from our global network provider, to ensure that even with a widespread outage on our primary provider's network, a completely separate network is on standby and ready to automatically take over all traffic if required.

We are thrilled to announce that as of April 2024, we have achieved SOC 2 Type 2 certification, complementing our existing ISO 27001 certification. This is a major step forward in our commitment to top-notch data security and privacy.

Read more here.

We've added dynamic destinations support to our official Terraform provider, as well as the ability to define monitoring status per destination. 

We've modified our regex match engine to be better in line with expectations. If a regex rule and full path redirect is set-up, we first check the ful path redirect, then the regex match, and fallback to the homepage. This ensures the visitor always lands at the correct destination.

We've reworked our API management in the redirect.pizza interface which adds some great additions:

• You may now create multiple API tokens under a single team
• You may label an API token with a descriptive name
• You can now see when an API token was last used
• You can now see how many calls per month are made per API token
• When generating an API token, you can only see the API token value once. After that, the API token is never shown again. This is conform best practice security practices.

Of course, our API keys are still automatically secret scanned on GitHub.