Changelog

We've partnered with Algomo to create a custom AI chat bot called Gino for our redirect.pizza free tier base. Gino can help you with setting up your first redirect, making the DNS change, or anything pizza related.

Live human chat is still available like expected for our paid customer base. Email support for our Free tier is still available as well.

This is a beta test; subject to change.

We’ve added a new {path:auto_trailing_slash} destination variable to be used in your destination. This variable automatically adds a trailing slash to the end of the variable value, if the path itself doesn’t end with a trailing slash, and the last segment doesn’t contain a dot (i.e. isn’t a file extension). This can be used for niche use-cases, where the destination always requires a trailing slash.

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