A very useful application for running and displaying applications rich in multimedia elementsMicrosoft DirectX is a group of technologies designed to make Windows-based PCs an ideal platform for running and displaying applications rich in multimedia elements such as full- color graphics, 3D animation, video and rich audio. |
Posted on January 10, 2006 in Websites by Jeff Starr
Welcome to Perishable Press! This article, Stupid htaccess Tricks, covers just about every htaccess “trick” in the book, and is easily the site’s most popular offering. In addition to this htaccess article, you may also want to explore the rapidly expanding htaccess tag archive. Along with all things htaccess, Perishable Press also focuses on (X)HTML, CSS, PHP, JavaScript, security, and just about every other aspect of web design, blogging, and online success. If these topics are of interest to you, I encourage you to subscribe to Perishable Press for a periodic dose of online enlightenment ;)
AllowOverridemod_rewrite
Apache server software provides distributed (i.e., directory-level) configuration via Hypertext Access files. These .htaccess files enable the localized fine-tuning of Apache’s universal system-configuration directives, which are defined in Apache’s main configuration file. The localized .htaccess directives must operate from within a file named .htaccess. The user must have appropriate file permissions to access and/or edit the .htaccess file. Further, .htaccess file permissions should never allow world write access — a secure permissions setting is “644”, which allows universal read access and user-only write access. Finally, .htaccess rules apply to the parent directory and all subdirectories. Thus to apply configuration rules to an entire website, place the .htaccess file in the root directory of the site.
Comments are essential to maintaining control over any involved portion of code. Comments in .htaccess code are fashioned on a per-line basis, with each line of comments beginning with a pound sign #. Thus, comments spanning multiple lines in the .htaccess file require multiple pound signs. Further, due to the extremely volatile nature of htaccess voodoo, it is wise to include only alphanumeric characters (and perhaps a few dashes and underscores) in any .htaccess comments.
As a configuration file, .htaccess is very powerful. Even the slightest syntax error (like a missing space) can result in severe server malfunction. Thus it is crucial to make backup copies of everything related to your site (including any original .htaccess files) before working with your Hypertext Access file(s). It is also important to check your entire website thoroughly after making any changes to your .htaccess file. If any errors or other problems are encountered, employ your backups immediately to restore original functionality.
.htaccess directives provide directory-level configuration without requiring access to Apache’s main server cofiguration file (httpd.conf). However, due to performance and security concerns, the main configuration file should always be used for server directives whenever possible. For example, when a server is configured to process .htaccess directives, Apache must search every directory within the domain and load any and all .htaccess files upon every document request. This results in increased page processing time and thus decreases performance. Such a performance hit may be unnoticeable for sites with light traffic, but becomes a more serious issue for more popular websites. Therefore, .htaccess files should only be used when the main server configuration file is inaccessible. See the “Performance Tricks” section of this article for more information.
## instructs the server to ignore the line. used for including comments. each line of comments requires it’s own #. when including comments, it is good practice to use only letters, numbers, dashes, and underscores. this practice will help eliminate/avoid potential server parsing errors.[F]403 Forbidden to the client.[L][N][G]Gone (no longer exists) status message.[P]mod_proxy[C][R][NC][PT]mod_rewrite to pass the rewritten URL back to Apache for further processing.[OR][NE][NS][QSA][S=x][E=variable:value][T=MIME-type][][]+[^][a-z]a{n}n, of the preceding character. e.g., x{3} matches exactly three x’s.a{n,}n or more of the preceding character. e.g., x{3,} matches three or more x’s.a{n,m}n and m, of the preceding character. e.g., x{3,7} matches three, four, five, six, or seven x’s.()^$?monzas? will match monza or monzas, while mon(za)? will match either mon or monza. i.e., x? matches zero or one of x.!!string” matches everything except “string”..-...domain.com.* - [F]”.+G+ matches one or more G’s, while "+" will match one or more characters of any kind.*.*” as a wildcard.|(x|y) matches x or y.\^ $ ! . * | ). e.g., use “\.” to indicate/escape a literal dot.\./*.*^$^.*$[^/.][^/.]+http://^domain.*domain”, which then may be proceeded by any number of any characters.^domain\.com$domain.com”.-d-f-sIt is an excellent idea to consistenly and logically comment your htaccess files. Any line in an htaccess file that begins with the pound sign ( # ) tells the server to ignore it. Multiple lines require multiple pounds and use letters/numbers/dash/underscore only:
# this is a comment# each line must have its own pound sign# use only alphanumeric characters along with dashes - and underscores _
Certain servers may not have “mod_rewrite” enabled by default. To ensure mod_rewrite (basic rewriting) is enabled throughout your site, add the following line once to your site’s root htaccess file:
# enable basic rewritingRewriteEngine on
Enable symbolic links (symlinks) by adding the following directive to the target directory’s htaccess file. Note: for the FollowSymLinks directive to function, AllowOverride Options privileges must be enabled from within the server configuration file (see proceeding paragraph for more information):
# enable symbolic linksOptions +FollowSymLinks
For directives that require AllowOverride in order to function, such as FollowSymLinks (see above paragraph), the following directive must be added to the server configuration file. For performance considerations, it is important to only enable AllowOverride in the specific directory or directories in which it is required. In the following code chunk, we are enabling the AllowOverride privs only in the specified directory (/www/replace/this/with/actual/directory). Refer to this section for more information about AllowOverride and performance enhancement:
# enable allowoverride privileges<Directory /www/replace/this/with/actual/directory>
AllowOverride Options</Directory>
Not every system enjoys the extension-only format of htaccess files. Fortunately, you can rename them to whatever you wish, granted the name is valid on your system. Note: This directive must be placed in the server-wide configuration file or it will not work:
# rename htaccess filesAccessFileName ht.access
Note: If you rename your htaccess files, remember to update any associated configuration settings. For example, if you are protecting your htaccess file via FilesMatch, remember to inform it of the renamed files:
# protect renamed htaccess files<FilesMatch "^ht\.">
Order deny,allow
Deny from all</FilesMatch>
Save yourself time and effort by defining replicate rules for multiple virtual hosts once and only once via your httpd.conf file. Then, simply instruct your target htaccess file(s) to inherit the httpd.conf rules by including this directive:
RewriteOptions Inherit
Limit the extent to which htaccess files decrease performance by enabling AllowOverride only in required directories. For example, if AllowOverride is enabled throughout the entire site, the server must dig through every directory, searching for htaccess files that may not even exist. To prevent this, we disable the AllowOverride in the site’s root htaccess file and then enable AllowOverride only in required directories via the server config file (refer to this section for more information). Note: if you do not have access to your site’s server config file and also need AllowOverride privileges, do not use this directive:
# increase performance by disabling allowoverrideAllowOverride None
Prevent certain 500 error displays by passing the default character set parameter before you get there. Note: replace the “utf-8” below with the charset that your site is using:
# pass the default character setAddDefaultCharset utf-8
To increase performance on PHP enabled servers, add the following directive:
# preserve bandwidth for PHP enabled servers<ifmodule mod_php4.c>
php_value zlib.output_compression 16386</ifmodule>
Here we are disabling the digital signature that would otherwise identify the server:
# disable the server signatureServerSignature Off
Here we are instructing the server to synchronize chronologically according to the time zone of some specified state:
# set the server timezoneSetEnv TZ America/Washington
Here we are specifying the default email address for the server administrator:
# set the server administrator emailSetEnv SERVER_ADMIN default@domain.com
The htaccess genius over at askapache.com explains how to dramatically improve your site’s transfer speed by enabling file caching 3. Using time in seconds* to indicate the duration for which cached content should endure, we may generalize the htaccess rules as such (edit file types and time value to suit your needs):
# cache images and flash content for one month<FilesMatch ".(flv|gif|jpg|jpeg|png|ico|swf)$">Header set Cache-Control "max-age=2592000"</FilesMatch>
# cache text, css, and javascript files for one week<FilesMatch ".(js|css|pdf|txt)$">Header set Cache-Control "max-age=604800"</FilesMatch>
# cache html and htm files for one day<FilesMatch ".(html|htm)$">Header set Cache-Control "max-age=43200"</FilesMatch>
# implement minimal caching during site development<FilesMatch "\.(flv|gif|jpg|jpeg|png|ico|js|css|pdf|swf|html|htm|txt)$">Header set Cache-Control "max-age=5"</FilesMatch>
# explicitly disable caching for scripts and other dynamic files<FilesMatch "\.(pl|php|cgi|spl|scgi|fcgi)$">Header unset Cache-Control</FilesMatch>
# alternate method for file cachingExpiresActive OnExpiresDefault A604800 # 1 weekExpiresByType image/x-icon A2419200 # 1 monthExpiresByType application/x-javascript A2419200 # 1 monthExpiresByType text/css A2419200 # 1 monthExpiresByType text/html A300 # 5 minutes# disable caching for scripts and other dynamic files<FilesMatch "\.(pl|php|cgi|spl|scgi|fcgi)$">ExpiresActive Off</FilesMatch>
Here is an easy way to set the default language for pages served by your server (edit the language to suit your needs):
# set the default languageDefaultLanguage en-US
Likewise, here we are setting the default character set (edit to taste):
# set the default character setAddDefaultCharset UTF-8
# add various mime typesAddType application/x-shockwave-flash .swfAddType video/x-flv .flvAddType image/x-icon .ico
# send the language tag and default character set# AddType 'text/html; charset=UTF-8' htmlAddDefaultCharset UTF-8DefaultLanguage en-US
# limit server request methods to GET and PUTOptions -ExecCGI -Indexes -AllRewriteEngine onRewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK|OPTIONS|HEAD) RewriteRule .* - [F]
# process files according to server request methodScript PUT /cgi-bin/upload.cgiScript GET /cgi-bin/download.cgi
For those special occasions where certain file types need to be processed with some specific cgi script, let em know who sent ya:
# execute all png files via png-script.cgiAction image/png /cgi-bin/png-script.cgi
Add the following code block to your htaccess file to add an extra layer of security. Any attempts to access the htaccess file will result in a 403 error message. Of course, your first layer of defense to protect htaccess files involves setting htaccess file permissions via CHMOD to 644:
# secure htaccess file<Files .htaccess>
order allow,deny
deny from all</Files>
To restrict access to a specific file, add the following code block and edit the file name, “secretfile.jpg”, with the name of the file that you wish to protect:
# prevent viewing of a specific file<files secretfile.jpg>
order allow,deny
deny from all</files>
To restrict access to a variety of file types, add the following code block and edit the file types within parentheses to match the extensions of any files that you wish to protect:
<FilesMatch "\.(htaccess|htpasswd|ini|phps|fla|psd|log|sh)$">
Order Allow,Deny
Deny from all</FilesMatch>
Prevent unauthorized directory browsing by instructing the server to serve a “xxx Forbidden - Authorization Required” message for any request to view a directory. For example, if your site is missing it’s default index page, everything within the root of your site will be accessible to all visitors. To prevent this, include the following htaccess rule:
# disable directory browsingOptions All -Indexes
Conversely, to enable directory browsing, use the following directive:
# enable directory browsingOptions All +Indexes
Likewise, this rule will prevent the server from listing directory contents:
# prevent folder listingIndexIgnore *
And, finally, the IndexIgnore directive may be used to prevent the display of select file types:
# prevent display of select file typesIndexIgnore *.wmv *.mp4 *.avi *.etc
This rule tells the server to search for and serve “business.html” as the default directory index. This rule must exist in the htaccess files of the root directory for which you wish to replace the default index file (e.g., “index.html”):
# serve alternate default index pageDirectoryIndex business.html
This rule is similar, only in this case, the server will scan the root directory for the listed files and serve the first match it encounters. The list is read from left to right:
# serve first available alternate default index page from seriesDirectoryIndex filename.html index.cgi index.pl default.htm
To enhance security, disguise scripting languages by replacing actual script extensions with dummy extensions of your choosing. For example, to change the “.foo” extension to “.php”, add the following line to your htaccess file and rename all affected files accordingly:
# serve foo files as php filesAddType application/x-httpd-php .foo
# serve foo files as cgi filesAddType application/x-httpd-cgi .foo
# limit access to local area network<Limit GET POST PUT>
order deny,allow
deny from all
allow from 192.168.0.0/33</Limit>
In the following example, all IP addresses are allowed access except for 12.345.67.890 and domain.com:
# allow all except those indicated here<Limit GET POST PUT>
order allow,deny
allow from all
deny from 12.345.67.890
deny from .*domain\.com.*</Limit>
In the following example, all IP addresses are denied access except for 12.345.67.890 and domain.com:
# deny all except those indicated here<Limit GET POST PUT>
order deny,allow
deny from all
allow from 12.345.67.890
allow from .*domain\.com.*</Limit>
This is how to block unwanted visitors based on the referring domain. You can also save bandwidth by blocking specific file types — such as .jpg, .zip, .mp3, .mpg — from specific referring domains. Simply replace “scumbag” and “wormhole” with the offending domains of your choice:
# block visitors referred from indicated domains<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTP_REFERER} scumbag\.com [NC,OR]
RewriteCond %{HTTP_REFERER} wormhole\.com [NC,OR]
RewriteRule .* - [F]</ifModule>
There are several effective ways to block a range of IP addresses via htaccess. This first method blocks an IP range specified by their CIDR (Classless Inter-Domain Routing) number. This method is useful for blocking mega-spammers such as RIPE, Optinet, and others. If, for example, you find yourself adding line after line of Apache deny directives for addresses beginning with the same first few numbers, choose one of them and try a whois lookup. Listed within the whois results will be the CIDR value representing every IP address associated with that particular network. Thus, blocking via CIDR is an effective way to eloquently prevent all IP instances of the offender from accessing your site. Here is a generalized example for blocking by CIDR (edit values to suit your needs):
# block IP range by CIDR number<Limit GET POST PUT>
order allow,deny
allow from all
deny from 10.1.0.0/16
deny from 80.0.0/8</Limit>
Likewise, to allow an IP range by CIDR number:
# allow IP range by CIDR number<Limit GET POST PUT>
order deny,allow
deny from all
allow from 10.1.0.0/16
allow from 80.0.0/8</Limit>
Another effective way to block an entire range of IP addresses involves truncating digits until the desired range is represented. As an IP address is read from left to right, its value represents an increasingly specific address. For example, a fictitious IP address of 99.88.77.66 would designate some uniquely specific IP address. Now, if we remove the last two digits (66) from the address, it would represent any address beginning with the remaining digits. That is, 99.88.77 represents 99.88.77.1, 99.88.77.2, … 99.88.77.99, …etc. Likewise, if we then remove another pair of digits from the address, its range suddenly widens to represent every IP address 99.88.x.y, where x and y represent any valid set of IP address values (i.e., you would block 256*256 = 65,536 unique IP addresses). Following this logic, it is possible to block an entire range of IP addresses to varying degrees of specificity. Here are few generalized lines exemplifying proper htaccess syntax (edit values to suit your needs):
# block IP range by address truncation<Limit GET POST PUT>
order allow,deny
allow from all
deny from 99.88.77.66
deny from 99.88.77.*
deny from 99.88.*.*
deny from 99.*.*.*</Limit>
Likewise, to allow an IP range by address truncation:
# allow IP range by address truncation<Limit GET POST PUT>
order deny,allow
deny from all
allow from 99.88.77.66
allow from 99.88.77.*
allow from 99.88.*.*
allow from 99.*.*.*</Limit>
Save a little space by blocking multiple IP addresses or ranges on one line. Here are few examples (edit values to suit your needs):
# block two unique IP addressesdeny from 99.88.77.66 11.22.33.44# block three ranges of IP addressesdeny from 99.88 99.88.77 11.22.33
Likewise, to allow multiple IP addresses or ranges on one line:
# allow two unique IP addressesallow from 99.88.77.66 11.22.33.44# allow three ranges of IP addressesallow from 99.88 99.88.77 11.22.33
Here are few miscellaneous rules for blocking various types of IP addresses. These rules may be adapted to allow the specified IP values by simply changing the deny directive to allow. Check ’em out (edit values to suit your needs):
# block a partial domain via network/netmask valuesdeny from 99.1.0.0/255.255.0.0
# block a single domaindeny from 99.88.77.66
# block domain.com but allow sub.domain.comorder deny,allowdeny from domain.comallow from sub.domain.com
To serve ‘em some unexpected alternate content when hotlinking is detected, employ the following code, which will protect all files of the types included in the last line (add more types as needed). Remember to replace the dummy path names with real ones. Also, the name of the nasty image being served in this case is “eatme.jpe”, as indicated in the line containing the RewriteRule. Please advise that this method will also block services such as FeedBurner from accessing your images.
# stop hotlinking and serve alternate content<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?domain\.com/.*$ [NC]
RewriteRule .*\.(gif|jpg)$ http://www.domain.com/eatme.jpe [R,NC,L]</ifModule>
Note: To deliver a standard (or custom, if configured) error page instead of some nasty image of the Fonz, replace the line containing the RewriteRule in the above htaccess directive with the following line:
# serve a standard 403 forbidden error pageRewriteRule .*\.(gif|jpg)$ - [F,L]
Note: To grant linking permission to a site other than yours, insert this code block after the line containing the “domain.com” string. Remember to replace “goodsite.com” with the actual site domain:
# allow linking from the following siteRewriteCond %{HTTP_REFERER} !^http://(www\.)?goodsite\.com/.*$ [NC]
Eliminate some of the unwanted scum from your userspace by injecting this handy block of code. After such, any listed agents will be denied access and receive an error message instead. Please advise that there are much more comprehensive lists available this example has been truncated for business purposes. Note: DO NOT include the “[OR]” on the very last RewriteCond or your server will crash, delivering “500 Errors” to all page requests.
# deny access to evil robots site rippers offline browsers and other nasty scumRewriteBase /RewriteCond %{HTTP_USER_AGENT} ^Anarchie [OR]RewriteCond %{HTTP_USER_AGENT} ^ASPSeek [OR]RewriteCond %{HTTP_USER_AGENT} ^attach [OR]RewriteCond %{HTTP_USER_AGENT} ^autoemailspider [OR]RewriteCond %{HTTP_USER_AGENT} ^Xaldon\ WebSpider [OR]RewriteCond %{HTTP_USER_AGENT} ^Xenu [OR]RewriteCond %{HTTP_USER_AGENT} ^Zeus.*Webster [OR]RewriteCond %{HTTP_USER_AGENT} ^ZeusRewriteRule ^.* - [F,L]
Or, instead of delivering a friendly error message (i.e., the last line), send these bad boys to the hellish website of your choice by replacing the RewriteRule in the last line with one of the following two examples:
# send em to a hellish website of your choiceRewriteRule ^.*$ http://www.hellish-website.com [R,L]
Or, to send em to a virtual blackhole of fake email addresses:
# send em to a virtual blackhole of fake email addressesRewriteRule ^.*$ http://english-61925045732.spampoison.com [R,L]
You may also include specific referrers to your blacklist by using HTTP_REFERER. Here, we use the infamously scummy domain, “iaea.org” as our blocked example, and we use “yourdomain” as your domain (the domain to which you are blocking iaea.org):
RewriteCond %{HTTP_REFERER} ^http://www.iaea.org$RewriteRule !^http://[^/.]\.yourdomain\.com.* - [F,L]
Note: Although these redirect techniques are aimed at blocking and redirecting nasty scumsites, the directives may also be employed for friendly redirection purposes:
# redirect any request for anything from spamsite to differentspamsiteRewriteCond %{HTTP_REFERER} ^http://.*spamsite.*$ [NC]RewriteRule .* http://www.differentspamsite.com [R]
# redirect all requests from spamsite to an image of something at differentspamsiteRewriteCond %{HTTP_REFERER} ^http://.*spamsite.*$ [NC]RewriteRule .* http://www.differentspamsite/something.jpg [R]
# redirect traffic from a certain address or range of addresses to another siteRewriteCond %{REMOTE_ADDR} 192.168.10.*RewriteRule .* http://www.differentspamsite.com/index.html [R]
Here is a step-by-step series of code blocks that should equip you with enough knowledge to block any/all necessary entities. Read through the set of code blocks, observe the patterns, and then copy, combine and customize to suit your specific scum-blocking needs:
# set variables for user agents and referers and ip addressesSetEnvIfNoCase User-Agent ".*(user-agent-you-want-to-block|php/perl).*" BlockedAgentSetEnvIfNoCase Referer ".*(block-this-referrer|and-this-referrer|and-this-referrer).*" BlockedRefererSetEnvIfNoCase REMOTE_ADDR ".*(666.666.66.0|22.22.22.222|999.999.99.999).*" BlockedAddress
# set variable for any class B network coming from a given netblockSetEnvIfNoCase REMOTE_ADDR "66.154.*" BlockedAddress
# set variable for two class B networks 198.25.0.0 and 198.26.0.0SetEnvIfNoCase REMOTE_ADDR "198.2(5|6)\..*" BlockedAddress
# deny any matches from above and send a 403 denied<Limit GET POST PUT>
order deny,allow
deny from env=BlockedAgent
deny from env=BlockedReferer
deny from env=BlockedAddress
allow from all</Limit>
Here is an excellent online tool for generating the necessary elements for a password-protected directory:
# password protect directories
htaccess Password Generator
Secure site contents by requiring user authentication for specified files and/or directories. The first example shows how to password-protect any single file type that is present beneath the directory which houses the htaccess rule. The second rule employs the FilesMatch directive to protect any/all files which match any of the specified character strings. The third rule demonstrates how to protect an entire directory. The fourth set of rules provides password-protection for all IP’s except those specified. Remember to edit these rules according to your specific needs.
# password-protect single file<Files secure.php>AuthType BasicAuthName "Prompt"AuthUserFile /home/path/.htpasswdRequire valid-user</Files>
# password-protect multiple files<FilesMatch "^(execute|index|secure|insanity|biscuit)*$">AuthType basicAuthName "Development"AuthUserFile /home/path/.htpasswdRequire valid-user</FilesMatch>
# password-protect the directory in which this htaccess rule residesAuthType basicAuthName "This directory is protected"AuthUserFile /home/path/.htpasswdAuthGroupFile /dev/nullRequire valid-user
# password-protect directory for every IP except the one specified# place in htaccess file of a directory to protect that entire directoryAuthType BasicAuthName "Personal"AuthUserFile /home/path/.htpasswdRequire valid-userAllow from 99.88.77.66Satisfy Any
Here is an excellent method for requiring SSL (via askapache.com 3):
# require SSLSSLOptions +StrictRequireSSLRequireSSLSSLRequire %{HTTP_HOST} eq "domain.tld"ErrorDocument 403 https://domain.tld
# require SSL without mod_sslRewriteCond %{HTTPS} !=on [NC]RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
This method is great for ensuring the CHMOD settings for various file types. Employ the following rules in the root htaccess file to affect all specified file types, or place in a specific directory to affect only those files (edit file types according to your needs):
# ensure CHMOD settings for specified file types# remember to never set CHMOD 777 unless you know what you are doing# files requiring write access should use CHMOD 766 rather than 777# keep specific file types private by setting their CHMOD to 400chmod .htpasswd files 640chmod .htaccess files 644chmod php files 600
This method will disguise all file types (i.e., any file extension) and present them as .php files (or whichever extension you choose):
# diguise all file extensions as phpForceType application/x-httpd-php
One method to help protect your server against DOS attacks involves limiting the maximum allowable size for file uploads. Here, we are limiting file upload size to 10240000 bytes, which is equivalent to around 10 megabytes. For this rule, file sizes are expressed in bytes. Check here for help with various file size conversions. Note: this code is only useful if you actually allow users to upload files to your site.
# protect against DOS attacks by limiting file upload sizeLimitRequestBody 10240000
Prevent malicious brainiacs from actively scripting secure directories by adding the following rules to the representative htaccess file (edit file types to suit your needs):
# secure directory by disabling script executionAddHandler cgi-script .php .pl .py .jsp .asp .htm .shtml .sh .cgiOptions -ExecCGI
Add the following htaccess rules to minimize or even eliminate CSS background-image “flickering” in MSIE6:
# minimize image flicker in IE6ExpiresActive OnExpiresByType image/gif A2592000ExpiresByType image/jpg A2592000ExpiresByType image/png A2592000
Replicate the following patterns to serve your own set of custom error pages. Simply replace the “/errors/###.html” with the correct path and file name. Also change the “###” preceding the path to summon pages for other errors. Note: your custom error pages must be larger than 512 bytes in size or they will be completely ignored by Internet Explorer:
# serve custom error pagesErrorDocument 400 /errors/400.htmlErrorDocument 401 /errors/401.htmlErrorDocument 403 /errors/403.htmlErrorDocument 404 /errors/404.htmlErrorDocument 500 /errors/500.html
# provide a universal error documentRewriteCond %{REQUEST_FILENAME} !-fRewriteCond %{REQUEST_FILENAME} !-dRewriteRule ^.*$ /dir/error.php [L]
This bit of voodoo will auto-correct simple spelling errors in the URL:
# automatically corect simple speling erors<IfModule mod_speling.c>
CheckSpelling On</IfModule>
Here is a useful method for delivering multimedia file downloads to your users. Typically, browsers will attempt to play or stream such files when direct links are clicked. With this method, provide a link to a multimedia file and a dialogue box will provide users the choice of saving the file or opening it. Here are a few htaccess rules demonstrating the technique (edit file types according to your specific needs):
# instruct browser to download multimedia filesAddType application/octet-stream .aviAddType application/octet-stream .mpgAddType application/octet-stream .wmvAddType application/octet-stream .mp3
There are many situations where site owners may wish to display the contents of a dynamic file rather than executing it as a script. To exercise this useful technique, create a directory in which to place dynamic files that should be displayed rather than executed, and add the following line of code to the htaccess file belonging to that directory. This method is known to work for .pl, .py, and .cgi file-types. Here it is:
RemoveHandler cgi-script .pl .py .cgi
During web development, maintenance, or repair, send your visitors to an alternate site while retaining full access for yourself. This is a very useful technique for preventing visitor confusion or dismay during those awkward, web-development moments. Here are the generalized htaccess rules to do it (edit values to suit your needs):
# redirect all visitors to alternate site but retain full access for youErrorDocument 403 http://www.alternate-site.comOrder deny,allowDeny from allAllow from 99.88.77.66
Here is another possible solution for "hiding" your site during those private, site-under-construction moments. Here we are instructing Apache to provide visitors with a password prompt while providing open access to any specifically indicated IP addresses or URL’s. Edit the following code according to your IP address and other development requirements (thanks to Caleb at askapache.com for sharing this trick 3):
# password prompt for visitorsAuthType basicAuthName "This site is currently under construction"AuthUserFile /home/path/.htpasswdAuthGroupFile /dev/nullRequire valid-user# allow webmaster and any others open accessOrder Deny,AllowDeny from allAllow from 111.222.33.4Allow from favorite.validation/services/Allow from googlebot.comSatisfy Any
Prevent viewing of all pictures of Fonzi during the midnight hour — or any files during any time period — by using this handy htaccess ruleset:
# prevent access during the midnight hourRewriteCond %{TIME_HOUR} ^12$RewriteRule ^.*$ - [F,L]
# prevent access throughout the afternoonRewriteCond %{TIME_HOUR} ^(12|13|14|15)$RewriteRule ^.*$ - [F,L]
For all redirects using the mod_rewrite directive, it is necessary to have the RewriteEngine enabled. It is common practice to enable the mod_rewrite directive in either the server configuration file or at the top of the site’s root htaccess file. If the mod_rewrite directive is not included in either of these two places, it should be included as the first line in any code block that utilizes a rewrite function (i.e., mod_rewrite), but only needs to be included once for each htaccess file. The proper mod_rewrite directive is included here for your convenience, but may or may not also be included within some of the code blocks provided in this article:
# initialize and enable rewrite engineRewriteEngine on
This method uses a “301 redirect” to establish a permanent redirect from the “www-version” of a domain to its respectively corresponding “non-www version”. Be sure to test immediately after preparing 301 redirects and remove it immediately if any errors occur. Use a “server header checker” to confirm a positive 301 response. Further, always include a trailing slash “/” when linking directories. Finally, be consistent with the “www” in all links (either use it always or never).
# permanently redirect from www domain to non-www domainRewriteEngine onOptions +FollowSymLinksRewriteCond %{HTTP_HOST} ^www\.domain\.tld$ [NC]RewriteRule ^(.*)$ http://domain.tld/$1 [R=301,L]
For a basic domain change from “old-domain.com” to “new-domain.com” (and folder/file names have not been changed), use the Rewrite rule to remap the old domain to the new domain. When checking the redirect live, the old domain may appear in the browser’s address bar. Simply check an image path (right-click an image and select “properties”) to verify proper redirection. Remember to check your site thoroughly after implementing this redirect.
# redirect from old domain to new domainRewriteEngine OnRewriteRule ^(.*)$ http://www.new-domain.com/$1 [R=301,L]
For example, if we wanted to redirect any requests containing the character string, “perish”, to our main page at http://perishablepress.com/, we would replace “some-string” with “perish” in the following code block:
# redirect any variations of a specific character string to a specific addressRewriteRule ^some-string http://www.domain.com/index.php/blog/target [R]
Here are two other methods for accomplishing string-related mapping tasks:
# map URL variations to the same directory on the same serverAliasMatch ^/director(y|ies) /www/docs/target
# map URL variations to the same directory on a different serverRedirectMatch ^/[dD]irector(y|ies) http://domain.com
Redirect an entire site via 301:
# redirect an entire site via 301redirect 301 / http://www.domain.com/
Redirect a specific file via 301:
# redirect a specific file via 301redirect 301 /current/currentfile.html http://www.newdomain.com/new/newfile.html
Redirect an entire site via permanent redirect:
# redirect an entire site via permanent redirectRedirect permanent / http://www.domain.com/
Redirect a page or directory via permanent redirect:
# redirect a page or directoryRedirect permanent old_file.html http://www.new-domain.com/new_file.htmlRedirect permanent /old_directory/ http://www.new-domain.com/new_directory/
Redirect a file using RedirectMatch:
# redirect a file using RedirectMatchRedirectMatch 301 ^.*$ http://www.domain.com/index.html
Note: When redirecting specific files, use Apache‘s Redirect rule for files within the same domain. Use Apache‘s RewriteRule for any domains, especially if they are different. The RewriteRule is more powerful than the Redirect rule, and thus should serve you more effectively.
Thus, use the following for a stronger, harder page redirection (first line redirects a file, second line a directory, and third a domain):
# redirect files directories and domains via RewriteRuleRewriteRule http://old-domain.com/old-file.html http://new-domain.com/new-file.htmlRewriteRule http://old-domain.com/old-dir/ http://new-domain.com/new-dir/RewriteRule http://old-domain.com/ http://new-domain.com/
This rule will ensure that all visitors are viewing pages via the subdomain of your choice. Edit the "subdomain", "domain", and "tld" to match your subdomain, domain, and top-level domain respectively:
# send visitors to a subdomainRewriteCond %{HTTP_HOST} !^$RewriteCond %{HTTP_HOST} !^subdomain\.domain\.com$ [NC]RewriteRule ^/(.*)$ http://subdomain.domain.tld/$1 [L,R=301]
# rewrite only if the file is not foundRewriteCond %{REQUEST_FILENAME} !-fRewriteRule ^(.+)special\.html?$ cgi-bin/special/special-html/$1
# rewrite only if an image is not foundRewriteCond %{REQUEST_FILENAME} !-fRewriteRule images/special/(.*).gif cgi-bin/special/mkgif?$1
# seo-friendly rewrite rules for various directoriesRewriteRule ^(.*)/aud/(.*)$ $1/audio-files/$2 [L,R=301]RewriteRule ^(.*)/img/(.*)$ $1/image-files/$2 [L,R=301]RewriteRule ^(.*)/fla/(.*)$ $1/flash-files/$2 [L,R=301]RewriteRule ^(.*)/vid/(.*)$ $1/video-files/$2 [L,R=301]
# broswer sniffing via htaccess environmental variablesRewriteCond %{HTTP_USER_AGENT} ^Mozilla.*RewriteRule ^/$ /index-for-mozilla.html [L]RewriteCond %{HTTP_USER_AGENT} ^Lynx.*RewriteRule ^/$ /index-for-lynx.html [L]RewriteRule ^/$ /index-for-all-others.html [L]
# redirect query to Google searchOptions +FollowSymlinksRewriteEngine OnRewriteCond %{REQUEST_URI} .google\.php*RewriteRule ^(.*)$ ^http://www.google.com/search?q=$1 [R,NC,L]
# deny request according to the request methodRewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK|OPTIONS|HEAD)$ [NC]RewriteRule ^.*$ - [F]
# redirect uploads to a better placeRewriteCond %{REQUEST_METHOD} ^(PUT|POST)$ [NC]RewriteRule ^(.*)$ /cgi-bin/upload-processor.cgi?p=$1 [L,QSA]
# seo friendly redirect for a single fileRedirect 301 /old-dir/old-file.html http://domain.com/new-dir/new-file.html
# seo friendly redirect for multiple files# redirects all files in dir directory with first letters xyzRedirectMatch 301 /dir/xyz(.*) http://domain.com/$1
# seo friendly redirect entire site to a different domainRedirect 301 / http://different-domain.com
Protect your insecure WordPress contact forms against online unrighteousness by verifying the domain from whence the form is called. Remember to replace the “domain.com” and “contact.php” with your domain and contact-form file names, respectively.
# secure wordpress contact forms via referrer checkRewriteCond %{HTTP_REFERER} !^http://www.domain.com/.*$ [NC]RewriteCond %{REQUEST_POST} .*contact.php$RewriteRule .* - [F]
In our article, The htaccess rules for all WordPress Permalinks, we revealed the precise htaccess directives used by the WordPress blogging platform for permalink functionality. Here, for the sake of completeness, we repeat the directives only. For more details please refer to the original article:
If WordPress is installed in the site’s root directory, WordPress creates and uses the following htaccess directives:
# BEGIN WordPress<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]</IfModule># END WordPress
If WordPress is installed in some subdirectory “foo”, WordPress creates and uses the following htaccess directives:
# BEGIN WordPress<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /foo/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /foo/index.php [L]</IfModule># END WordPress
# activate SSI for HTML and or SHTML file typesAddType text/html .htmlAddType text/html .shtmlAddHandler server-parsed .htmlAddHandler server-parsed .shtmlAddHandler server-parsed .htm
# grant CGI access in a specific directoryOptions +ExecCGIAddHandler cgi-script cgi pl# to enable all scripts in a directory use the followingSetHandler cgi-script
# turn off magic_quotes_gpc for PHP enabled servers<ifmodule mod_php4.c>
php_flag magic_quotes_gpc off</ifmodule>
Note: enabling this option may result in a relative decrease in server performance.
# enable MD5 digests via ContentDigestContentDigest On
# send Atom and RSS requests to the site docroot to be rewritten for ExpressionEngineRewriteRule .*atom.xml$ http://www.yoursite.com/index.php/weblog/rss_atom/ [R]RewriteRule .*rss.xml$ http://www.yoursite.com/index.php/weblog/rss_2.0/ [R]
# cause all requests for index.html to be rewritten for ExpressionEngineRewriteRule /.*index.html$ http://www.domain.com/index.php [R]
[MXTDS-009] Anri Hoshizaki, Hinata Komine – MAXING 3D
MAXING 3D！ 小峰ひなた 星崎アンリ
発売日： 2011/01/16
収録時間： 240分
出演者： 小峰ひなた 星崎アンリ
監督： Araki
シリーズ： MAXING 3D！
メーカー： マキシング
レーベル： MAXING 3D！
ジャンル： 3D ギャル
品番： h_068mxtds009
1.20 GB
[KOG-007] Tomomi Takahara – Erotic Cum Body 7
くねるエロボディと卑猥な中出しデート7 高原智美
発売日： 2009/05/13
収録時間： 120分
出演者： 高原智美
監督： —-
シリーズ： くねるエロボディと卑猥な中出しデート
メーカー： AVS
レーベル： 個人
ジャンル： ギャル パンスト レオタード 中出し ローション
品番： 33kog007so
AVI 986mb
[JAG-050] Yayoi Iha – Make Love Shot Active OL
素人口説き撮り 現役OL 弥生
発売日： 2011/01/13
収録時間： 120分
出演者： —-
監督： —-
シリーズ： 素人口説き撮り
メーカー： ハヤブサ
レーベル： JAGUAR
ジャンル： 美乳 OL スレンダー 素人 3P、4P
品番： 28jag050so
AVI 1.23gb
[IESP-530] Seira Moroboshi – Apartment Complex Wife Misery 20
団地妻の憂い 諸星セイラ
発売日： 2010/02/04
収録時間： 125分
出演者： 諸星セイラ（百瀬涼）
監督： —-
シリーズ： 団地妻の憂い
メーカー： アイエナジー
レーベル： 暴夢
ジャンル： 人妻 単体作品 3P、4P DVDトースター
品番： 1iesp530
AVI 1.34gb
[ETC-81] Reiko Sawamura – The Counseling Center
美熟女Hな悩み相談所～性の悩みから人生相談まで澤村レイコがお答え致します～
発売日： 2011/01/06
収録時間： 150分
出演者： 澤村レイコ（高坂保奈美、高坂ますみ）
監督： —-
シリーズ： —-
メーカー： グローリークエスト
レーベル： Et cetera
ジャンル： 企画 童貞 イラマチオ
品番： 13etc81
AVI 1.50gb
[ANB-14] Hitomi Araki – Incest Big Tits My Aunt
綺麗でいやらしい叔母さんの豊かな乳房と巨尻に埋もれる僕
貸出開始日： 2011/01/08
収録時間： 100分
出演者： 荒木瞳
監督： —-
シリーズ： 綺麗でいやらしい叔母さん
メーカー： ルビー
レーベル： NOBLE
ジャンル： 熟女 ぽっちゃり
品番： 17anb14r
AVI 917mb
[EMAS-063] Reiko Mashida – Incest Dirty Mom and Son
近親相姦 息子を痴女るいやらしい体をしたドスケベ熟女10
発売日： 2011/01/01
収録時間： 120分
出演者： 真下礼子
監督： ロック
シリーズ： 息子を痴女るいやらしい体をしたドスケベ熟女
メーカー： エマニエル
レーベル： SA（エマニエル）
ジャンル： 義母 熟女 痴女 近親相姦 中出し
品番： emas063
AVI 1.17gb
[SIKA-18] Sumire Morishita – Incest Mom
近親相姦 五十路の母 森下すみれ
発売日： 2009/08/06
収録時間： 80分
出演者： 森下すみれ
監督： AKAGI
シリーズ： 近親相姦 ○○の母
メーカー： センタービレッジ
レーベル： 匠（センタービレッジ）
ジャンル： クンニ 熟女 人妻 近親相姦
品番： h_086sika18
AVI 1.67gb
[UURU-54] Kazumi Shimura – Incest Mom at Night Home
中出し近親相姦 夜のお母さん 我が家の24時 志村和美
発売日： 2010/12/30
収録時間： 100分
出演者： 志村和美
監督： 銀玉一郎
シリーズ： 中出し近親相姦
メーカー： センタービレッジ
レーベル： あじさい
ジャンル： 熟女 人妻 近親相姦 中出し
品番： h_086uuru54
AVI 873mb
[HONE-72] Kanami Minasawa – Incest Mom Nakadashi
近親相姦 デカ黒ちくびの母 皆澤奏美
発売日： 2010/12/30
収録時間： 85分
出演者： 皆澤奏美
監督： ジョニー別府
シリーズ： 近親相姦 ○○の母
メーカー： センタービレッジ
レーベル： 花園（センタービレッジ）
ジャンル： 熟女 人妻 近親相姦
品番： h_086hone72
AVI 789mb
