.htaccess - Revision history

Rootadminacc: /* Password protected directory */

2013-04-24T13:07:22Z

Password protected directory

← Older revision		Revision as of 14:07, 24 April 2013
Line 96:		Line 96:
	require valid-user</pre>		require valid-user</pre>

	Generator the .htpasswd file content [http://www.htpasswdgenerator.~~com/apache/htaccess.html~~ here] and then do:		Generator the .htpasswd file content [http://www.htpasswdgenerator.net here] and then do:

	vim .htpasswd		vim .htpasswd
Line 107:		Line 107:
	http://httpd.apache.org/docs/2.2/mod/core.html<br>		http://httpd.apache.org/docs/2.2/mod/core.html<br>
	http://httpd.apache.org/docs/2.2/howto/htaccess.html#how<br>		http://httpd.apache.org/docs/2.2/howto/htaccess.html#how<br>
			http://www.htpasswdgenerator.com/apache/htaccess.html<br>
	http://www.sitepoint.com/forums/showthread.php?396553-htaccess-Doesn-t-Work		http://www.sitepoint.com/forums/showthread.php?396553-htaccess-Doesn-t-Work

Rootadminacc: /* Password protected directory */

2013-02-11T13:45:01Z

Password protected directory

← Older revision		Revision as of 14:45, 11 February 2013
Line 85:		Line 85:
	== Password protected directory ==		== Password protected directory ==

	See [[Scripts#eXample_.htaccess_and_.htpasswd_file this]] guide too.		See [[Scripts#eXample_.htaccess_and_.htpasswd_file \| this]] guide too.

	cd '''into''' the directory you want to protect.		cd '''into''' the directory you want to protect.

Rootadminacc: /* Password protected directory */

2013-02-11T13:44:52Z

Password protected directory

← Older revision		Revision as of 14:44, 11 February 2013
Line 84:		Line 84:

	== Password protected directory ==		== Password protected directory ==

			See [[Scripts#eXample_.htaccess_and_.htpasswd_file this]] guide too.

	cd '''into''' the directory you want to protect.		cd '''into''' the directory you want to protect.

Rootadminacc: /* Force lower-case URLs */

2013-01-31T16:35:48Z

Force lower-case URLs

← Older revision		Revision as of 17:35, 31 January 2013
Line 39:		Line 39:
	== Force lower-case URLs ==		== Force lower-case URLs ==

	http://stackoverflow.com/questions/10458998/rewriting-url-to-all-lowercase?lq=1		http://stackoverflow.com/questions/10458998/rewriting-url-to-all-lowercase?lq=1<br>
	http://stackoverflow.com/questions/6852277/case-sensitive-urls-how-to-make-them-insensitive?lq=1		http://stackoverflow.com/questions/6852277/case-sensitive-urls-how-to-make-them-insensitive?lq=1<br>
	http://stackoverflow.com/questions/2923658/convert-to-lowercase-in-a-mod-rewrite-rule		http://stackoverflow.com/questions/2923658/convert-to-lowercase-in-a-mod-rewrite-rule<br>
	http://www.chrisabernethy.com/force-lower-case-urls-with-mod_rewrite		http://www.chrisabernethy.com/force-lower-case-urls-with-mod_rewrite

Rootadminacc: /* Broken URLs and running HTML as PHP */

2013-01-31T16:35:32Z

Broken URLs and running HTML as PHP

← Older revision		Revision as of 17:35, 31 January 2013
Line 36:		Line 36:

	in the .htaccess file.		in the .htaccess file.

			== Force lower-case URLs ==

			http://stackoverflow.com/questions/10458998/rewriting-url-to-all-lowercase?lq=1
			http://stackoverflow.com/questions/6852277/case-sensitive-urls-how-to-make-them-insensitive?lq=1
			http://stackoverflow.com/questions/2923658/convert-to-lowercase-in-a-mod-rewrite-rule
			http://www.chrisabernethy.com/force-lower-case-urls-with-mod_rewrite

	== [http://codex.wordpress.org/Changing_File_Permissions Wordpress File Permissions] ==		== [http://codex.wordpress.org/Changing_File_Permissions Wordpress File Permissions] ==

Rootadminacc at 16:33, 31 January 2013

2013-01-31T16:33:37Z

← Older revision		Revision as of 17:33, 31 January 2013
Line 4:		Line 4:
	locate .htaccess</pre>		locate .htaccess</pre>

	You may need to run [[~~General_Linux~~#~~updatedb~~ \| updatedb]] first.		You may need to run [[Linux#updatedb_.28locate_command.29 \| updatedb]] first.

	== Permalinks ==		== Permalinks ==

Rootadminacc: /* Password protected directory */

2013-01-16T11:25:58Z

Password protected directory

@@ Line 77: / Line 77: @@
 == Password protected directory ==
 Guides:
 http://httpd.apache.org/docs/2.0/howto/auth.html<br>
 http://httpd.apache.org/docs/2.2/mod/core.html<br>

Rootadminacc: Created page with "It's default permissions/group (if you want to create it for example) are 644 -rw-r--r-- and ftpuser:psacln (for a Plesk server). To find .htaccess either go to /var/www/vhost..."

2013-01-15T11:42:22Z

Created page with "It's default permissions/group (if you want to create it for example) are 644 -rw-r--r-- and ftpuser:psacln (for a Plesk server). To find .htaccess either go to /var/www/vhost..."

New page

It's default permissions/group (if you want to create it for example) are 644 -rw-r--r-- and ftpuser:psacln (for a Plesk server). To find .htaccess either go to /var/www/vhosts/domain/httpdocs and do ls -la or the following command:

<pre>find /var/www/vhosts/ .htaccess | grep htaccess
locate .htaccess</pre>

You may need to run [[General_Linux#updatedb | updatedb]] first.

== Permalinks ==

Temporarily change the file from 644 (default permissions are -rw-r--r-- and ftpuser:psacln) by doing:

<pre>chmod 766 .htaccess</pre>

<pre># BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /press/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /press/index.php [L]
</IfModule>
# END WordPress</pre>

Now go to the Wordpress backend, log in and go to Settings > Permalinks > Custom Structure (normally /%postname%/) and click Save Changes. It will likely say "''You should update your .htaccess now.''" so make a blog post to test and it should work. You can now set the .htaccess file back to 644 or even 604 now.

[http://codex.wordpress.org/Using_Permalinks Wordpress Permalinks guide]

== Broken URLs and running HTML as PHP ==

If a Wordpress site on a development URL was working fine and you have changed some of the permalinks and the site cannot be accessed it is likely because .htaccess is missing this syntax: <pre>"Options +FollowSymLinks" </pre>

To force .html files to run as a php scripts put the following:

<pre>AddHandler php-script .html</pre>

in the .htaccess file.

== [http://codex.wordpress.org/Changing_File_Permissions Wordpress File Permissions] ==

== Wordpress Install: The mysql extension was not found ==

If you get the following message when installing Wordpress through the one click installer in the Applications tab of Plesk: "''Unable to install the app on website because hosting settings of this website do not meet the installation requirements. These requirements are listed below. The mysql extension was not found.''"

You need to rename the .htaccess file temporarily (cd into dir, mv .htaccess <filename>), uninstall/install Wordpress and then you can rename it back. It is due to the following: http://kb.parallels.com/en/111427

== Mod_rewrite ==

Mod_rewrite may be enabled by default on an Ubuntu VPS, [http://dev.antoinesolutions.com/apache-server/mod_rewrite CentOS guide]. This is located in /etc/apache2/mods-enabled/

Search the following to confirm.

<pre>/etc/apache2/mods-enabled# locate rewrite.load
/etc/apache2/mods-available/rewrite.load
/etc/apache2/mods-enabled/rewrite.load</pre>

During a drupal install it should test for this anyway and tell you. During the install you can either use drupal built in rewrites or use the .htaccess equivalent. The .htaccess file will be in /var/www/vhosts/yourdomain.com/httpdocs , /var/www/vhosts/lvpsIP-IP-IP-IP.vps.webfusion.co.uk/site1 or make it yourself. If so just make sure you have the below 2 lines in here or else mod_rewrite will not work.

Options +Indexes 
RewriteEngine on

== Options +Indexes ==

This will allow you to list the directory of a folder when viewing it in a browser, as long as it has the correct permissions (normally www-data:www-data). This can be applied to only specific folders by putting the .htaccess file in the folder you want it to affect.

To deny indexing, use -Indexes instead.

== Options +FollowSymLinks ==

Add the above option into a .htaccess file if you get the following message in the Apache log:

''Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden''

Add it if you also get the below error on Wordpress sites:

''Forbidden, perhaps you need to change the file permissions for this document or upload an index page''

== Password protected directory ==

Guides:

http://www.htpasswdgenerator.com/apache/htaccess.html 
http://httpd.apache.org/docs/2.0/howto/auth.html 
http://httpd.apache.org/docs/2.2/mod/core.html 
http://httpd.apache.org/docs/2.2/howto/htaccess.html#how 
http://www.sitepoint.com/forums/showthread.php?396553-htaccess-Doesn-t-Work

Need AllowOverride

[http://www.edwinbush.com/my-tools-page/htpasswd-content-generator .htpasswd content generator]

== Redirect 301 ==

Point an entire site to a different URL, the first slash is for the domain's htaccess you are in redirected to example.com:

<pre># This allows you to redirect your entire website to any other domain
Redirect 301 / http://example.com/</pre>

Redirect index.html to a specific subfolder:

<pre># This allows you to redirect index.html to a specific subfolder
Redirect /index.html http://example.com/newdirectory/</pre>

Redirect an old file to a new file path:

<pre># Redirect old file path to new file path
Redirect /olddirectory/oldfile.html http://example.com/newdirectory/newfile.html</pre>

Redirect to a specific index page:

<pre># Provide Specific Index Page (Set the default handler)
DirectoryIndex index.html</pre>

Also include Options +FollowSymLinks

== [http://blogs.digitss.com/apache/allow-only-https-access-with-htaccess Allow only HTTPS access with htaccess] ==
== [http://www.highrankings.com/forum/index.php?showtopic=35833 mod_rewrite https to http] ==

A HTTPS request will have to open the file ".htaccess" to pick the redirect to HTTP. The certificate will be therefore sent to the customer; showing the invalid warning.

The only way to bypass this is to buy a SSL certificate.

== [http://wordpress.org/support/topic/disabling-flash-uploader?replies=2#post-2493931 Whitelist Flash in mod_security] ==

[http://wordpress.org/support/topic/wp-321-image-upload-http-error#post-2408792 Details of the problem]

== Windows ==

One solution is http://www.helicontech.com/ape/ as it provides support for Apache .htacces and .htpasswd configuration files in Microsoft IIS.