Server Config · Apache 2.4 · Live Rule Simulator

.htaccess Tester & Rule Generator

Build and test Apache web server configuration files. Enforce HTTPS, manage 301 redirects, block malicious IPs, enable Gzip compression, and verify routing behavior with the built-in request simulator.

Presets:

Live Apache URL & IP Simulator

Simulate Incoming Request URL:

Simulate Client IP:

403 Forbidden—Request blocked: Client IP 203.0.113.19 matches blocked list.

Core Redirects & Canonicalization

Force HTTPS (Redirect HTTP to HTTPS via 301)

Domain Canonicalization (WWW preference):

Performance & Security Modules

Custom Path Redirects (2)

→

Blocked IP Addresses (1 per line)

Live .htaccess OutputApache 2.4+ Ready

# ==============================================================================
# SpeedDrain Optimized .htaccess Configuration
# Generated on 2026-11-02
# ==============================================================================

# Prevent Directory Browsing
Options -Indexes

# Block Access to Sensitive Configuration Files
<FilesMatch "^\.(htaccess|htpasswd|env|git)">
  Require all denied
</FilesMatch>

# Deny Access from Malicious IPs
<RequireAll>
  Require all granted
  Require not ip 198.51.100.42
  Require not ip 203.0.113.19
</RequireAll>

# Custom Error Pages
ErrorDocument 404 /404.html
ErrorDocument 500 /500.html

# Initialize Rewrite Engine
<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /

  # Force HTTPS protocol
  RewriteCond %{HTTPS} off
  RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

  # Canonicalize to Non-WWW (e.g. www.example.com -> example.com)
  RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
  RewriteRule ^(.*)$ https://%1/$1 [R=301,L]

  # Custom 301/302 Redirect Rules
  RewriteRule ^old-about$ /about [R=301,L]
  RewriteRule ^legacy-api/(.*)$ /v2/$1 [R=301,L]

</IfModule>

# Security Headers
<IfModule mod_headers.c>
  Header set X-Content-Type-Options "nosniff"
  Header set X-Frame-Options "SAMEORIGIN"
  Header set X-XSS-Protection "1; mode=block"
  Header set Referrer-Policy "strict-origin-when-cross-origin"
  Header set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" env=HTTPS
</IfModule>

# Enable Gzip / Deflate Compression
<IfModule mod_deflate.c>
  AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css
  AddOutputFilterByType DEFLATE application/javascript application/json application/xml
  AddOutputFilterByType DEFLATE image/svg+xml
</IfModule>

# Leverage Browser Caching (mod_expires)
<IfModule mod_expires.c>
  ExpiresActive On
  ExpiresDefault "access plus 1 month"
  ExpiresByType text/html "access plus 1 hour"
  ExpiresByType text/css "access plus 1 year"
  ExpiresByType application/javascript "access plus 1 year"
  ExpiresByType image/webp "access plus 1 year"
  ExpiresByType image/jpeg "access plus 1 year"
  ExpiresByType image/png "access plus 1 year"
  ExpiresByType image/svg+xml "access plus 1 year"
</IfModule>

Apache RewriteEngine Architecture & Redirect Codes

Understanding Apache mod_rewrite Directives & Flags

The Apache HTTP Server rewrite module (mod_rewrite) rewrites requested URLs on the fly based on regular expression rules:

RewriteEngine On: Activates the runtime URL rewriting engine for the current directory scope and its children.
RewriteCond: Defines a conditional predicate that must evaluate to true before the following RewriteRule will execute (e.g. %{HTTPS} off).
[R=301,L]: Flags appended in brackets. R=301 instructs the server to issue an HTTP 301 status redirect to the browser, while L (Last) prevents further rewrite evaluation if this rule matches.
[NC]: No Case flag, making the regular expression pattern case-insensitive.

HTTP 301 vs. HTTP 302: SEO & Caching Ramifications

Selecting the appropriate redirection status code is vital for search engine rankings and link equity preservation:

301 Moved Permanently

Passes 90–99% of PageRank link authority to the target URL. Browsers and search engine indexers cache 301 redirects aggressively. Ideal for permanent URL restructuring, domain rebranding, and HTTPS enforcement.

302 Found (Temporary)

Signals to web crawlers that the move is short-lived. Search engines retain the original URL in index rankings and do not transfer authority. Ideal for A/B testing, seasonal promotions, or temporary maintenance redirects.