Redirect rule generation

Generate Nginx, Apache, and Cloudflare redirect text from the old path, new path, status code, and query options.

Local browser processing
This page has passed the public directory check; full functionality is available after enabling JavaScript.
User Guide

How to Generate Redirect Rules

Redirect rule generation processes input only in the current browser; it does not upload, connect to the internet, or write to persistent storage.

  1. Enter a path

    Enter the old path and target path; the default example is /old-docs to /docs/start.

  2. Select a rule

    Select 301/302/307/308, and decide whether to retain the query.

  3. Copy configuration

    Copy the rules for each target platform separately, then perform syntax and regression checks in the target environment before deployment.

Limitations and Notes

  • Paths are treated only as strings; the tool does not check whether the target exists or is safe.
  • Different server versions and contexts may require adjustments to the configuration location and escaping.
  • The tool will not request URL, modify the server, or claim that the configuration overrides all security policies.

FAQ

Will it access the destination address?

No, the sole purpose is to generate text.

Why is the query preservation syntax different?

The configuration syntax for Nginx, Apache, and Cloudflare differs, so the tool generates the corresponding text separately.

Can it generate permanent redirects?

You can choose 301, but confirm the caching and rollback strategies before going live.

Page feedbackFound an issue or have suggestions for improvement?
Feedback features need to be used in the online version

Please enable JavaScript in the online version before submitting; local features of the current tool or example are not affected.

Go to the online version for feedback