Force HTTPS jump: judge non-HTTPS requests through RewriteCond and permanently redirect to HTTPS with R=301; 2. Remove file extensions: use !-f and !-d conditions to rewrite as /about as /about.php; 3. Force www or without www: match through HTTP_HOST and jump 301 to unified domain name format; 4. Customize pseudo-static URL: parse /article/123/title to /article.php?id=123; 5. Prevent image link theft: Check the Referer header, return the prompt image or 403 if it is not from this site; 6. Multi-condition combination redirection: match malicious crawlers through HTTP_USER_AGENT and jump to blocked page; 7. Simple URL redirection: Jump the old page 301 to the new page to maintain SEO weight; 8. Turn on beautiful URL: point all non-file and non-directory requests to index.php to support front-end controller mode; all rules need to take effect after RewriteEngine On is turned on. It is recommended to test and backup configuration items one by one to prevent errors from causing unavailability of the service.

Apache RewriteRule is a powerful feature provided by Apache's mod_rewrite module for rewriting URL requests. It is often used to implement SEO-friendly links, website jumps, prevent link theft, and forced HTTPS jumps. Here are several common and practical RewriteRule examples for .htaccess files or Apache virtual host configurations.

1. Force HTTPS jump

Redirect all HTTP requests to HTTPS:

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

• RewriteCond %{HTTPS} off : determines whether it is currently non-HTTPS.
• R=301 : Return to 301 Permanent redirect.
• L : It means that this is the last rule and will not be processed in the future.

Suitable for scenarios where HTTPS is required for the entire site.

2. Remove file extensions (such as .html or .php)

Hide the .php extension, such as accessing /about actually loading /about.php :

 RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([a-zA-Z0-9_-] )$ $1.php [L]

• !-f and !-d : Make sure that the requested file or directory is not a real existing one, and avoid conflicts.
• ^([a-zA-Z0-9_-] )$ : Match URLs without extensions.
• $1.php : Internal rewrite to the .php file of the same name.

.php can be replaced with .html , which works for static pages.

3. Forced to bring www or not domain names

Forced www:

 RewriteEngine On
RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]

Forced to not bring www (more common):

 RewriteEngine On
RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
RewriteRule ^(.*)$ https://example.com/$1 [L,R=301]

• [NC] : Ignore case.
• Using 301 jumps is beneficial to SEO to unify domain name weights.

4. Customize pseudo-static URL (such as the article ID is displayed as the title)

Rewrite /article/123/my-great-article to /article.php?id=123 :

 RewriteEngine On
RewriteRule ^article/([0-9] )/([a-zA-Z0-9_-] )$ /article.php?id=$1 [L]

• The first bracket captures the article ID.
• The second bracket captures the title (for SEO only, negligible).
• The actual processing still uses id parameter.

This method makes the URL more friendly while the backend logic remains unchanged.

5. Prevent image link thieves

Block other websites from directly referring to your image resources:

 RewriteEngine On
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^https://(www\.)?yourdomain\.com/.*$ [NC]
RewriteRule \.(jpg|jpeg|png|gif|webp)$ https://yourdomain.com/nohotlinking.jpg [R,L]

• Check if Referer header is empty (allows direct access) or comes from your domain name.
• Match common image formats and return prompt image when link stolen.

Can be replaced with a return 403 status code:

 RewriteRule \.(jpg|jpeg|png|gif)$ - [F,L]

6. Multi-condition combination: Redirect only to specific user agents

For example: Block some crawlers or redirect mobile users:

 RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^BadBot [NC,OR]
RewriteCond %{HTTP_USER_AGENT} SpamBot [NC]
RewriteRule ^.*$ https://example.com/blocked.html [R,L]

• OR represents the "or" relationship, and the next condition is triggered only if it is met.
• Used to block malicious crawlers or test robots.

7. Simple URL redirection (old page → new page)

 RewriteRule ^old-page\.html$ /new-page.html [R=301,L]

• Suitable for keeping old links available after the website is redesigned.
• Use R=301 to tell the search engine that it has been migrated permanently.

8. Enable "Pretty URLs" support (such as commonly used in PHP frameworks)

For example, frameworks such as Laravel, Symfony, etc. need to point all requests to index.php :

 RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1 [QSA,L]

• QSA : Keep the original query parameters (such as ?id=1 ).
• Suitable for Front Controller mode.

Tips

• Turn on RewriteEngine : All rules must have RewriteEngine On .
• Test order : The rules are executed in order, and note that L flag is used to avoid subsequent interference.
• Debugging tips : You can use RewriteLog (old version) or pass the 404 log curl -I test to jump.
• Scope : The path in .htaccess does not have leading / , and may need to be adjusted in the virtual host.

Basically these common scenarios. It is recommended to test one by one when actually using it to avoid accidental damage to normal requests. RewriteRule is powerful, but a regular error may cause the entire website to be inaccessible. It is best to back up the configuration before modification.

The above is the detailed content of Apache rewrite rule examples. For more information, please follow other related articles on the PHP Chinese website!