.htaccess - Revision history

Christoph at 21:41, 15 April 2015

2015-04-15T21:41:54Z

Christoph: /* Standardise web address */

2015-04-15T21:37:28Z

‎Standardise web address

Christoph: /* See also */

2012-12-21T00:56:47Z

‎See also

Christoph: /* Prevent hotlinking of images */

2012-12-21T00:51:38Z

‎Prevent hotlinking of images

Christoph: /* Enable SSI */

2012-12-21T00:50:30Z

‎Enable SSI

Christoph at 23:59, 20 December 2012

2012-12-20T23:59:11Z

Christoph: /* Other */

2012-05-30T23:23:09Z

‎Other

Christoph at 02:54, 25 March 2007

2007-03-25T02:54:38Z

Christoph at 02:52, 25 March 2007

2007-03-25T02:52:21Z

Christoph: /* External links */

2007-01-24T04:04:29Z

‎External links

← Older revision		Revision as of 21:41, 15 April 2015
Line 1:		Line 1:
−	'''<code>.htaccess</code>''' (''Hypertext Access'') is the default name of [[Apache ~~HTTP Server~~\|Apache's]] directory-level configuration file. It provides the ability to customize configuration directives defined in the main configuration file. The configuration directives need to be in <code>.htaccess</code> context and the user needs appropriate permissions.	+	'''<code>.htaccess</code>''' (''Hypertext Access'') is the default name of [[Apache\|Apache's]] directory-level configuration file. It provides the ability to customize configuration directives defined in the main configuration file. The configuration directives need to be in <code>.htaccess</code> context and the user needs appropriate permissions.

	==Common usage==		==Common usage==

@@ Line 87: / Line 87: @@
 *Permanent address change: suppose your site has permanently moved to a new domain. The following rules apply said changes:
   RewriteCond %{HTTP_HOST} ^www.domain.com$ [NC]
-  RewriteRule  ^(.*)$ http://www.domain2.com/$1  [R=301, L]
+  RewriteRule  ^(.*)$ <nowiki>http://www.domain2.com/$1</nowiki>  [R=301, L]
 Here "<code>[NC]</code>" means case insensitive and its called "<code>RewriteCond</code> Flags". <code>[R=301]</code> means "moved permanently". It is called a redirection header code.

@@ Line 132: / Line 132: @@
 *[[Mod_rewrite|mod_rewrite]]
 *[[Apache HTTP Server]]
-*[[Configuration file]]
+*[[LAMP]]
 ==External links==

@@ Line 57: / Line 57: @@
 :If someone was to visit <nowiki>http://www.example.com/page1.html</nowiki>, they would be sent (with an [[HTTP]] status code of 302) to <nowiki>http://www.example.com/page2.html</nowiki>.
-===Prevent [[Bandwidth theft|hotlinking]] of images===
+===Prevent bandwidth theft / hotlinking of images===
 The following <code>.htaccess</code> rules use [[mod rewrite]].

@@ Line 34: / Line 34: @@
   Satisfy any
-===Enable [[Server_Side_Includes|SSI]]===
+===Enable Server Side Includes (SSI)===
   AddType text/html .shtml
   AddHandler server-parsed .shtml

@@ Line 1: / Line 1: @@
-'''.htaccess''' (''Hypertext Access'') is the default name of [[Apache HTTP Server|Apache's]] directory-level configuration file. It provides the ability to customize configuration directives defined in the main configuration file. The configuration directives need to be in ''.htaccess'' context and the user needs appropriate permissions.
+'''<code>.htaccess</code>''' (''Hypertext Access'') is the default name of [[Apache HTTP Server|Apache's]] directory-level configuration file. It provides the ability to customize configuration directives defined in the main configuration file. The configuration directives need to be in <code>.htaccess</code> context and the user needs appropriate permissions.
 ==Common usage==
@@ Line 5: / Line 5: @@
   ErrorDocument 404 my404page.html
-:This code can be used to create any custom page. Certain pages are more complicated to modify - if you create a custom [[404 error|404]] Forbidden page, then a viewer will not see the custom page. Here is an example showing a method used to get around this:
+:This code can be used to create any custom page. Certain pages are more complicated to modify &mdash; if you create a custom [[404 error|404]] Forbidden page, then a viewer will not see the custom page. Here is an example showing a method used to get around this:
   ErrorDocument 404 /public/my404page.html
-:In this case you would need another .htaccess file in /public, containing these lines:
+:In this case you would need another <code>.htaccess</code> file in <code>/public</code>, containing these lines:
   Order allow,deny
@@ Line 58: / Line 58: @@
 ===Prevent [[Bandwidth theft|hotlinking]] of images===
-The following .htaccess rules use [[mod rewrite]].
+The following <code>.htaccess</code> rules use [[mod rewrite]].
 ====From specific domains====
@@ Line 75: / Line 75: @@
 :Unless the image is displayed on <nowiki>example.com</nowiki>, browers would see the image hotlink.gif.
-Note: Hotlink protection using .htaccess relies on the client sending the correct "Referer" value in the http GET request. Programs such as Windows Media Player send a blank referrer, so that attempts to use .htaccess to protect movie files for example are ineffective.
+Note: Hotlink protection using <code>.htaccess</code> relies on the client sending the correct "Referer" value in the http GET request. Programs such as Windows Media Player send a blank referrer, so that attempts to use <code>.htaccess</code> to protect movie files for example are ineffective.
 ====Standardise web address====
@@ Line 83: / Line 83: @@
   RewriteRule (.*) <nowiki>http://www.example.com/$1</nowiki> [R=Permanent]
-If anyone types in your sites address without the 'www' prefix, this will redirect them to the page with the 'www' prefix
+If anyone types in your sites address without the '<code>www</code>' prefix, this will redirect them to the page ''with'' the '<code>www</code>' prefix
 ====Dynamic ''vs.'' static URLs====
@@ Line 103: / Line 109: @@
   RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /index\.php\?product=([^&]+)&make=([^&]+)&year=([^\ ]+)\ HTTP/
   RewriteRule ^index\.php$ <nowiki>http://example.com/product/%1/%2/%3?</nowiki> [R=301,L]
 ==Directory rules==
-A .htaccess file controls the directory it is in, '''plus all subdirectories'''. However, by placing additional .htaccess files in the subdirectories, this can be overruled.
+A <code>.htaccess</code> file controls the directory it is in, '''plus all subdirectories'''. However, by placing additional <code>.htaccess</code> files in the subdirectories, this can be overruled.
 ==User permissions==
-The user permissions for .htaccess are controlled on server level with the ''AllowOverride'' directive which is documented in the Apache Server Documentation.
+The user permissions for <code>.htaccess</code> are controlled on server level with the <code>AllowOverride</code> directive which is documented in the Apache Server Documentation.
 ==Other uses==
-Some web developers have modified .htaccess to perform custom tasks server-side before serving content to the browser. Developer Shaun Inman shows it is possible to edit .htaccess to [http://www.shauninman.com/plete/2005/08/css-constants allow for Server Side Constants] within [[Cascading Style Sheets|CSS]].
+Some web developers have modified <code>.htaccess</code> to perform custom tasks server-side before serving content to the browser. Developer Shaun Inman shows it is possible to edit <code>.htaccess</code> to [http://www.shauninman.com/plete/2005/08/css-constants allow for Server Side Constants] within [[Cascading Style Sheets|CSS]].
 ==See also==

@@ Line 133: / Line 133: @@
 *[http://www.informit.com/articles/article.asp?p=29967&rl=1 Restricting Website Access with Apache 2]
 *[http://www.howtoforge.com/htaccess_authentication .htaccess Based Authentication On Subdirectories]
-*[http://www.askapache.com/2006/htaccess/htaccesselite-ultimate-htaccess-article.html#force-filetype-with-forcetype Ultimate htaccess article]
+*[http://www.askapache.com/htaccess/htaccess.html Ultimate htaccess article] &mbash; by AskApache
 [[Category:World Wide Web]]

@@ Line 50: / Line 50: @@
   DirectoryIndex homepage.html
-:Here, anyone visiting http://www.example.com/ would see the homepage.html page, rather than the default index.html.
+:Here, anyone visiting <nowiki>http://www.example.com/</nowiki> would see the homepage.html page, rather than the default index.html.
 ===Redirects===
   Redirect page1.html page2.html
-:If someone was to visit http://www.example.com/page1.html, they would be sent (with an [[HTTP]] status code of 302) to http://www.example.com/page2.html
+:If someone was to visit <nowiki>http://www.example.com/page1.html</nowiki>, they would be sent (with an [[HTTP]] status code of 302) to <nowiki>http://www.example.com/page2.html</nowiki>.
 ===Prevent [[Bandwidth theft|hotlinking]] of images===
@@ Line 73: / Line 73: @@
   RewriteRule \.(gif|jpg)$ <nowiki>http://www.example.com/hotlink.gif</nowiki> [R,L]
-:Unless the image is displayed on example.com, browers would see the image hotlink.gif.
+:Unless the image is displayed on <nowiki>example.com</nowiki>, browers would see the image hotlink.gif.
 Note: Hotlink protection using .htaccess relies on the client sending the correct "Referer" value in the http GET request. Programs such as Windows Media Player send a blank referrer, so that attempts to use .htaccess to protect movie files for example are ineffective.
@@ Line 102: / Line 102: @@
   # Externally redirect client requests for old dynamic URLs to equivalent new static  URLs
   RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /index\.php\?product=([^&]+)&make=([^&]+)&year=([^\ ]+)\ HTTP/
-  RewriteRule ^index\.php$ http://example.com/product/%1/%2/%3? [R=301,L]
+  RewriteRule ^index\.php$ <nowiki>http://example.com/product/%1/%2/%3?</nowiki> [R=301,L]
 ==Directory rules==
@@ Line 114: / Line 114: @@
 ==See also==
-* [[Robots.txt|robots.txt]]
+*[[Robots.txt|robots.txt]]
-* [[Mod_rewrite|mod_rewrite]]
+*[[Mod_rewrite|mod_rewrite]]
 *[[Apache HTTP Server]]
 *[[Configuration file]]

@@ Line 101: / Line 101: @@
 ==External links==
+===Apache.org===
-*[http://www.javascriptkit.com/howto/htaccess.shtml Easy to understand tutorial]
-* [http://www.javascriptkit.com/howto/htaccess.shtml Comprehensive guide to .htaccess]
 *[http://httpd.apache.org/docs/1.3/mod/mod_rewrite.html Documentation for mod_rewrite], frequently used in .htaccess files
 *[http://httpd.apache.org/docs/mod/directive-dict.html#Context Apache configuration directives allowed in .htaccess context]
 *[http://httpd.apache.org/docs/howto/htaccess.html Apache Docs .htaccess Howto]
 *[http://www.mousewhisperer.co.uk/php_page.html Beginner's .htaccess tutorial and Custom Error Page Generator] - Beginner's tutorial on .htaccess and custom error page generator in [[PHP]]
-*[http://cooletips.de/htaccess/ htaccess File Generator at cooletips.de]
+*[http://cooletips.de/htaccess/ .htaccess File Generator at cooletips.de]
 *[http://www.myhtaccess.com Repository of .htaccess/mod_rewrite snippets, examples and tricks]
-* [http://httpd.apache.org/docs/2.0/howto/auth.html Authentication, Authorization and Access Control]
+*[http://www.informit.com/articles/article.asp?p=29967&rl=1 Restricting Website Access with Apache 2]
-* [http://www.informit.com/articles/article.asp?p=29967&rl=1 Restricting Website Access with Apache 2]
+*[http://www.howtoforge.com/htaccess_authentication .htaccess Based Authentication On Subdirectories]
 [[Category:World Wide Web]]