Changelog

We've made a few small improvements to our analytics page:

• You can easily apply filters by clicking on a table row on the analytics page. This will apply the filters directly.
• When you have certain filters active and navigate to a different view or use our share link, the filters are now kept.
• Bug squashing: exporting the redirect analytics with tag filters applied previously resulted in a black screen in the PDF. This has now been fixed!

We've added the ability to view the following in your Raw Analytics per incoming request:

• Continent
• Subdivision (i.e. state/province)
• City

You can filter on these variables by utilizing the new filters:

• "continent:US"
• "subdivision:CA"

We're excited to announce that we now provide high-performance nameservers to use for redirecting your domains.

By utilizing our nameservers, your DNS records are directly pointed to redirect.pizza.

Find your own nameserver combination at your Team Settings.

Important: only use these nameservers if you understand the implication for your domain. We only recommend using these nameservers if you wish to redirect all traffic (including all subdomains) to your domain.

Read more here.

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 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.

redirect.pizza now provides an official easy-to-use Zapier Actions to easily create or update a redirect in redirect.pizza based on a trigger from another app.

Want to create a redirect when you add it to a Google Sheet? Want to create a redirect when you launch a new website? Set up a Zap with Zapier and you're on your way.

Read more

• Added an `Accept` header to both the tester & destination monitor.
• Added a banner for when a payment is overdue with a payment update link.
• Optimized the user invite flow
• Optimized the DNS checker and increased checking frequency.
• Fixed an issue with specific Azure SSO configurations for SAML2

We've expanded our Edge network with 4 more locations for an even better redirect coverage around the world.

Big welcome to:

• Hawaii
• Johannesburg
• Seattle
• Seoul

We've added the page title & page favicon to the 'frame' redirect type. This will ensure a title tag is set and the appropriate favicon is loaded.

We are proud to announce our broken destination monitoring feature!

With this feature enabled we'll periodically check all your redirect destinations. If unreachable, we'll list it in your dashboard and report a summary of broken destinations in the Summary email.

This feature is available from the Pro plan and up.

We've added API support for managing email forwards.

You may create, update & delete email forwards via the respective API calls.

See the updated documentation here.