Changelog

We've added X-Forwarded-For support to our Dedicated IPs to enable a middleware proxy to forward the client's IP.

This can be especially useful when using redirect.pizza as a headless redirect provider, where the redirect is executed within the CMS or CDN layer, powered by the powerful redirect.pizza matching engine. Passing along the correct client IP will result in a better analytical overview and the ability to steer traffic based on IP information, such as country.

Now you can keep up with the redirect.pizza changelog using good ol' RSS. Check out the feed here: redirect.pizza/changelog.rss

Small improvements matter: we’ve added the request duration to our redirect tester, so you can see how long it took to process your redirect.

We made it quicker and easier to delete a source URL from the redirect detail page. Simply click the three dots beside the source URL and select 'Delete' to remove it.

We are now supporting Apple Pay and Google Pay, thanks to our payment partner Paddle. Fast and secure subscriptions just got easier!

We’ve added a segments destination variable from 0 to 9 to be used as either a replacement tag or in dynamic destinations. This can be helpful when using partial path matching and then forwarding a specific path element to the destination.

For example, you have a request like example.com/test1/test2. In this case, you always want to use the second path segment. You can now use the segments variable: {segments.1}. The first segment of the path can be found under {segments.0}.

We’ve added a new API endpoint: apply automatic DNS. This endpoint can be called through a POST call to trigger the automatic DNS changes if configured in the account.

Each domain resource object now includes an automatic_dns resource. This indicates whether Automatic DNS is available for this domain and, if so, provides the URL to which the POST call should be sent to apply the DNS changes.

Read more about this change here.

We're happy to announce it's now possible to serve robots.txt files on your domains!

This can help block (bad) bots and get's you back in control how you want your domains to be indexed.

Serveral options are available:

• No robots.txt (default)

• Explicitly allow all

• Block bad bots

• Disallow all

• Custom (Dedicated IP only)

Read more here.