Review a migration first
Use 302 for an initial redirect from /old-guide to https://example.com/new-guide while you confirm the destination and query behavior.
Exact path redirect
Subset: a single literal source path and a simple absolute HTTP(S) destination. Query strings, fragments, percent escapes, wildcards, credentials, and configuration syntax are not accepted in the fields.
Server configuration snippet
Requires mod_rewrite and suitable AllowOverride permissions. The rule assumes a .htaccess at the document root; source patterns omit the initial slash.
This tool generates text and does not run or deploy configuration. Test server syntax and redirect behavior in staging. Check for loops if the destination resolves to the same host and path. Start with a temporary redirect when reviewing a migration; permanent responses may be cached.
No requests are made to either URL. Configuration remains local until you copy or download it.
How to use the Redirect Rule Generator
- 01
Enter a source path such as /old-guide and a simple absolute HTTP or HTTPS destination.
- 02
Choose a temporary or permanent redirect status and whether to preserve the incoming query string.
- 03
Select the server format, copy or download the snippet, then review it with the rest of your server configuration before deployment.
Examples
Preserve request methods
Choose 307 for a temporary relocation or 308 for a permanent relocation when the redirect must preserve the method, such as POST.
An exact file path
The Apache pattern for /old.html becomes ^old\.html$ in a root .htaccess. Escaping the dot prevents it from acting as a regex wildcard.
The supported subset
Source paths use ASCII letters, digits, slash, underscore, tilde, period, and hyphen. Dot segments, repeated slashes, wildcards, query strings, fragments, and percent escapes are rejected. Destinations are simple absolute HTTP(S) URLs with no query, fragment, credentials, or configuration characters. These restrictions keep the snippet understandable and prevent line or directive injection.
Server context changes the rule
Apache output assumes mod_rewrite in a document-root .htaccess, where the source pattern has no leading slash. It also needs the relevant server permissions. Nginx output is an exact-match location intended for an existing server block. Neither snippet is a complete server configuration, and both can interact with existing routing.
Query strings and method behavior
With preservation enabled, Apache keeps the incoming query for a destination that has none, while Nginx appends $is_args$args. With it disabled, Apache emits QSD and Nginx returns the bare destination. Status 301 or 302 may change POST to GET; 307 and 308 preserve the method when followed according to HTTP semantics.
What to know
- One exact ASCII path per snippet. No arbitrary regex, bulk migration, destination query string, configuration execution, or deployment.
Common questions
Will this deploy the redirect?
No. It prepares downloadable text. Use your normal configuration review, syntax check, staging test, and deployment process.
Why are arbitrary regex patterns unavailable?
An exact-path mapping is easier to validate and review. Wildcard or regex migrations require additional capture, escaping, ordering, and query decisions beyond this tool’s subset.
Can a valid snippet still create a loop?
Yes. If the destination routes back to the source, the redirects can loop. Check the effective hostname, scheme, path, proxy behavior, and other redirects together.