The "Redirect Except a Path" recipe offers a nuanced approach to website redirection, allowing Pro plan users to finely control which requests are subject to redirection. While conventional redirection recipes affect all incoming requests uniformly, this recipe empowers website owners to exempt a specific path from the redirection rule. This level of customization is valuable for various scenarios where redirecting all traffic may not be desirable, such as preserving specific sections of the website, ensuring uninterrupted access to critical resources, or accommodating complex site structures.

Example use case

  • Preserving a Subdirectory: Consider a website with a subdirectory containing a legacy application that is not compatible with HTTPS. The "Redirect Except a Path" recipe allows you to redirect all requests to HTTPS, except those to the subdirectory containing the legacy application. This ensures that the legacy application remains accessible to users, while the rest of the website is secured with HTTPS.
  • Protecting Administrative Paths: Administrative or backend paths critical for website management can be exempted, ensuring uninterrupted access for site administrators.
  • Customized User Journeys: For websites offering diverse user journeys, exempting specific paths enables a tailored experience, redirecting users globally while allowing exceptions for specialized content or services.

How to install this recipe on my website with

Installing this recipe on your website requires the following steps:

  1. Enter the path to ignore: In the form below, specify the path that should be exempted from redirection. All requests under this path will be excluded from the global redirection rule.
  2. Click on the "Install on my website" button: Execute the installation process by clicking the "Install" button. This action creates the necessary rules in "Draft" mode for redirecting all the requests, except the ones performed in this path.
  3. Review the created rules: Review the created rules to make sure that they accurately reflect your configuration. If necessary, you can edit the rules before publishing them on your website.
  4. Publish on your website: Finalize the installation by publishing the rules on your website.