Changelog

It's about the little things. You can now select between both 'http://' & 'https://' schema's in our tester.

Previously you could already prefix your tested URL with the right schema, but just pressing a link is easier right!

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.