Differences
This shows you the differences between two versions of the page.
| tutorials:htaccess [2011/04/30 13:45] – created clemens | tutorials:htaccess [2011/10/04 19:11] (current) – Fix formatting: ToC, readability of codelines. memnon | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Contents | Contents | ||
| - | - [[#intro|Introduction]] | + | - [[# |
| - | - [[#recipes|Recipes]] | + | - [[# |
| - | - [[#redir-error|Redirect to a custom error page]] | + | - [[#Redirect to a custom error page]] |
| - | - [[#deny-dir|Deny directory listing]] | + | - [[#Deny directory listing]] |
| - | - [[#addtype|Add (or force) MIME-type]] | + | - [[#Add (or force) MIME-type]] |
| - | - [[#no-ext|Access files without specifying the extension | + | - [[#Access files without specifying the extension |
| - | * [[#add-ext|I want to access files without extension, but my (cgi|pl|php) is not found]]]] | + | * [[#I want to access files without extension, but my (cgi|pl|php) is not found]]]] |
| - | - [[#remove-handler|Serve .pl .php .cgi etc. as plain text files]] | + | - [[#Serve .pl .php .cgi etc. as plain text files]] |
| - | - [[#download|Force a download with a specific filename]] | + | - [[#Force a download with a specific filename]] |
| - | - [[#charset|Specify a default character encoding]] | + | - [[#Specify a default character encoding]] |
| - | - [[#password|Password protect your directories]] | + | - [[#Password protect your directories]] |
| ===== Introduction ===== | ===== Introduction ===== | ||
| Line 19: | Line 19: | ||
| .htaccess is the default file used by the [[http:// | .htaccess is the default file used by the [[http:// | ||
| - | The configuration directives placed in a .htaccess file will take effect immediately when a document, located in the directory where the .htaccess file is located and all subdirectories, | + | The configuration directives placed in a .htaccess file will take effect immediately when a document, located in the directory where the .htaccess file is located and all subdirectories, |
| Remember that .htaccess files must be readable by the server, so you can "chmod 640 .htaccess" | Remember that .htaccess files must be readable by the server, so you can "chmod 640 .htaccess" | ||
| Line 26: | Line 26: | ||
| * [[http:// | * [[http:// | ||
| - | * [[http:// | + | * [[http:// |
| * [[http:// | * [[http:// | ||
| Line 41: | Line 41: | ||
| If you type http:// | If you type http:// | ||
| - | " | + | |
| ==== Add (or force) MIME-type ==== | ==== Add (or force) MIME-type ==== | ||
| Line 47: | Line 47: | ||
| The server could not be aware of all kind of files out there, so will have some troubles trying to figure out what to do with an unknown extension. You can tell the server what to do with unknown file types. Say you have a [[http:// | The server could not be aware of all kind of files out there, so will have some troubles trying to figure out what to do with an unknown extension. You can tell the server what to do with unknown file types. Say you have a [[http:// | ||
| - | " | + | |
| AddType is the directive, application/ | AddType is the directive, application/ | ||
| Line 53: | Line 53: | ||
| Even if the server knows what's the MIME-type of a specific file extension, you could prefer it to use another one. Let's say that you want .html files to be served as application/ | Even if the server knows what's the MIME-type of a specific file extension, you could prefer it to use another one. Let's say that you want .html files to be served as application/ | ||
| - | " | + | |
| You can look for common MIME-type on [[http:// | You can look for common MIME-type on [[http:// | ||
| Line 63: | Line 63: | ||
| You can use URIs without extensions with: | You can use URIs without extensions with: | ||
| - | " | + | |
| === I want to access files without extension, but my (cgi|pl|php) is not found === | === I want to access files without extension, but my (cgi|pl|php) is not found === | ||
| Line 69: | Line 69: | ||
| Suppose that you have a cgi file called script.cgi and that, **once you enable MultiViews** (see above), when you access http:// | Suppose that you have a cgi file called script.cgi and that, **once you enable MultiViews** (see above), when you access http:// | ||
| - | " | + | |
| If you have perl and/or php files, add (modify the extension as needed): | If you have perl and/or php files, add (modify the extension as needed): | ||
| - | " | + | |
| ==== Serve .pl .php .cgi etc. as plain text files ==== | ==== Serve .pl .php .cgi etc. as plain text files ==== | ||
| Line 79: | Line 79: | ||
| If you want the server to execute your files, in order to be able to read the code of some specific files, you can remove the handlers. Let's say that the code you want to read is located in $HOME/ | If you want the server to execute your files, in order to be able to read the code of some specific files, you can remove the handlers. Let's say that the code you want to read is located in $HOME/ | ||
| - | " | + | |
| ==== Force a download with a specific filename ==== | ==== Force a download with a specific filename ==== | ||
| Line 85: | Line 85: | ||
| Let's say that you have a pdf file with an unintuitive name aaa222.pdf. You might want to force a download when people access the file and, in doing so, specify a default file name for the file that will be saved. This will do the job: | Let's say that you have a pdf file with an unintuitive name aaa222.pdf. You might want to force a download when people access the file and, in doing so, specify a default file name for the file that will be saved. This will do the job: | ||
| - | " <Files x.cab& | + | <Files x.cab> Header set Content-Disposition " |
| ==== Specify a default character encoding ==== | ==== Specify a default character encoding ==== | ||
| Line 91: | Line 91: | ||
| If you want all your html documents to be served with UTF-8 as the default encoding (or charset): | If you want all your html documents to be served with UTF-8 as the default encoding (or charset): | ||
| - | " | + | |
| - | UTF-8 was used as an example, but you can use whatever encoding is appropriate. Note also that in the example only files with extension html will have a default encoding. If you want to extend that behaviour to other file extensions, add them on the same line. For instance, " | + | UTF-8 was used as an example, but you can use whatever encoding is appropriate. Note also that in the example only files with extension html will have a default encoding. If you want to extend that behaviour to other file extensions, add them on the same line. For instance, "//AddCharset UTF-8 .html .htm .txt//". |
| This can also be useful if you want that only pages written in a specific language are served with a default encoding, while the others use the encoding sent normally by the server. So, suppose that you're usin [[http:// | This can also be useful if you want that only pages written in a specific language are served with a default encoding, while the others use the encoding sent normally by the server. So, suppose that you're usin [[http:// | ||
| - | " | + | |
| only .cn.html files will have UTF-8 as the default encoding. (The order of the language in the extension is not relevant, i.e., the files could have been html.en and html.cn; also, the leading dot in the extension in the .htaccess file is optional). | only .cn.html files will have UTF-8 as the default encoding. (The order of the language in the extension is not relevant, i.e., the files could have been html.en and html.cn; also, the leading dot in the extension in the .htaccess file is optional). | ||
| Line 104: | Line 104: | ||
| This is a FAQ: http:// | This is a FAQ: http:// | ||
| + | |||