.htaccess Rule Generator

How this reads your output

Each line you write is matched against a set of known rule shapes and converted into the corresponding Apache directives, with rewrite rules grouped inside a single mod_rewrite block and module-dependent directives wrapped in the matching IfModule guard. Lines that are not recognised are reported rather than silently dropped, so nothing goes missing between what you asked for and what you deploy.

What the results mean

Needs mod_rewrite

Whether the output depends on the rewrite module. It is present on almost every Apache host, and the IfModule guard means the file still loads if it is not.

Lines not recognised

Requests that produced no directives. Check these, because a rule you asked for and did not get is the failure mode that matters.

Rule order

Rewrite rules are evaluated top to bottom and the first match with an L flag stops processing, so order changes behaviour.

Common problems and fixes

The site returns a 500 error after uploading the file

A syntax error, an unsupported directive, or a module that is not loaded. Apache refuses to serve rather than skipping the bad line. Restore the previous file immediately, then reintroduce rules one at a time. The server error log names the exact line, which is far quicker than guessing.

A redirect loops endlessly

Usually an HTTPS redirect behind a proxy or load balancer that terminates TLS. The server sees plain HTTP on every request, so the rule fires forever. Check the X-Forwarded-Proto header instead of the HTTPS variable in that setup. Conflicting www and HTTPS rules produce the same symptom when they redirect to each other.

Frequently asked questions

More in DevTools

• XML Sitemap GeneratorTurn a list of URLs into a valid sitemap.xml.
• JSON Tree ViewerExplore JSON as a collapsible tree, with the path of every value.