Generate Apache .htaccess files with redirects, security headers, caching rules, and access control directives.
This generator assembles Apache per-directory configuration for four jobs: URL redirects, HTTP response security headers, caching rules, and request access controls. Enter the policies you want, review the resulting directives, and place them in the .htaccess file for the directory they should govern. It runs in the browser and produces configuration text; it does not install or exercise that configuration on the web server. The common surprise is that valid-looking output is not automatically usable on every host. Apache must allow the relevant directive classes, and the modules providing those directives must be available.
The output is Apache configuration text organized around the requested behaviors. Redirect choices express URL routing, header choices set response metadata, caching choices describe cache policy, and access-control choices restrict requests. Read the assembled result as one ordered file because rules from separate sections can interact. The generator prepares the configuration; Apache decides whether each directive is allowed and applicable.
Apache evaluates .htaccess in directory context. A file normally affects its directory and descendants, subject to server configuration and more specific files. This is especially important for mod_rewrite: a RewriteRule pattern in per-directory context sees the URL path after the current directory prefix has been removed, so the path it matches never has a leading slash. Place generated rules at the directory scope for which they were composed.
No. .htaccess is an Apache per-directory configuration format, and its directives are not portable to Nginx or IIS configuration files. Translate the intended behavior into the target server's native syntax instead. Even on an Apache-compatible hosting service, confirm which directives, override classes, and modules the provider supports before replacing an existing file.
Apache may have rejected a directive in that directory context, encountered invalid syntax, or lacked a required module. Restore the last working configuration, then inspect the server error log or hosting diagnostics for the rejected line. Reintroduce generated sections individually. Successful generation confirms the text was produced, not that the destination server accepts every directive.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.