Password Protecting a Directory With ".htaccess" - Revision history

Boom at 18:07, 1 March 2017

2017-03-01T18:07:29Z

← Older revision		Revision as of 12:07, 1 March 2017
Line 95:		Line 95:

	{{:Shared_Hosting}}		{{:Shared_Hosting}}
	[[Category:~~Shared_Hosting~~\|.htaccess]]		[[Category:Shared Hosting\|.htaccess]]

Boom at 18:07, 1 March 2017

2017-03-01T18:07:18Z

← Older revision		Revision as of 12:07, 1 March 2017
Line 94:		Line 94:
	http://httpd.apache.org/docs/mod/core.html#errordocument		http://httpd.apache.org/docs/mod/core.html#errordocument

	{{:~~Legacy_Shared_Hosting~~}}		{{:Shared_Hosting}}
	[[Category:~~Legacy Hosting~~\|.htaccess]]		[[Category:Shared_Hosting\|.htaccess]]

Boom: /* Format */

2017-03-01T18:06:45Z

Format

← Older revision		Revision as of 12:06, 1 March 2017
Line 29:		Line 29:
	The format of the file should be as follows, with no blank lines before the text begins:		The format of the file should be as follows, with no blank lines before the text begins:

	<pre>AuthUserFile /~~home~~/~~users~~/a/~~acctname~~/.passwordfile		<pre>AuthUserFile /var/www/vhosts/domain.tld/.passwordfile
	AuthGroupFile /dev/null		AuthGroupFile /dev/null
	AuthName 'Access For Valid Users'		AuthName 'Access For Valid Users'
Line 47:		Line 47:
	The <Limit> tag defines both what is allowed to be done in the directory, and the requirements for allowing someone into it.		The <Limit> tag defines both what is allowed to be done in the directory, and the requirements for allowing someone into it.
	<div class="messagebox metadata">'''Note''': If you have forms or cgi scripts in the protected directory, your limit should be set to <Limit GET POST>.</div>		<div class="messagebox metadata">'''Note''': If you have forms or cgi scripts in the protected directory, your limit should be set to <Limit GET POST>.</div>


	==Creating the Password File==		==Creating the Password File==

Jab at 19:25, 22 January 2014

2014-01-22T19:25:37Z

← Older revision		Revision as of 13:25, 22 January 2014
Line 95:		Line 95:
	http://httpd.apache.org/docs/mod/core.html#errordocument		http://httpd.apache.org/docs/mod/core.html#errordocument

			{{:Legacy_Shared_Hosting}}
	[[Category:Hosting\|htaccess]]		[[Category:Legacy Hosting\|.htaccess]]

Jab at 14:38, 9 April 2011

2011-04-09T14:38:40Z

← Older revision		Revision as of 08:38, 9 April 2011
Line 19:		Line 19:
	===Placement and Permissions===		===Placement and Permissions===

	The .htaccess file should be placed in the directory that you want to protect. The file should be owned by you with the group "www", and permissions set to 640. When this is done correctly, a long listing showing the file will look like this:		The .htaccess file should be placed in the directory that you want to protect. The file should be owned by you with the group "www-data", and permissions set to 640. When this is done correctly, a long listing showing the file will look like this:

	<pre>-rw-r----- 1 acctname www 170 Aug 24 2001 .htaccess</pre>		<pre>-rw-r----- 1 acctname www-data 170 Aug 24 2001 .htaccess</pre>

	<div class="messagebox metadata">'''Note''': You may set all public_html permissions to defaults by logging in to http://home.xmission.com/ and selecting the "My Account" tab. There, you will find a "Repair Your Web Permissions" option under the "XMission Tools" section.</div>		<div class="messagebox metadata">'''Note''': You may set all public_html permissions to defaults by logging in to http://home.xmission.com/ and selecting the "My Account" tab. There, you will find a "Repair Your Web Permissions" option under the "XMission Tools" section.</div>
Line 55:		Line 55:
	===Placement and Permissions===		===Placement and Permissions===

	The password file should be placed outside of your public_html directory for added security. Files in your root directory, outside public_html, can't be viewed from the web. The file should be owned by you with the group "www", and permissions set to 640. When this is done correctly, a long listing showing the file will look like this:		The password file should be placed outside of your public_html directory for added security. Files in your root directory, outside public_html, can't be viewed from the web. The file should be owned by you with the group "www-data", and permissions set to 640. When this is done correctly, a long listing showing the file will look like this:

	<pre>-rw-r----- 1 acctname www 170 Aug 24 2001 .passwordfile</pre>		<pre>-rw-r----- 1 acctname www-data 170 Aug 24 2001 .passwordfile</pre>

	<div class="messagebox metadata">'''Note''': You may set all public_html permissions to defaults by logging in to http://home.xmission.com/ and selecting the "My Account" tab. There, you will find a "Repair Your Web Permissions" option under the "XMission Tools" section.</div>		<div class="messagebox metadata">'''Note''': You may set all public_html permissions to defaults by logging in to http://home.xmission.com/ and selecting the "My Account" tab. There, you will find a "Repair Your Web Permissions" option under the "XMission Tools" section.</div>

Cyeates at 18:06, 19 May 2009

2009-05-19T18:06:44Z

← Older revision		Revision as of 12:06, 19 May 2009
Line 96:		Line 96:


	~~{{footer}}~~
	[[Category:Hosting\|htaccess]]		[[Category:Hosting\|htaccess]]

Pashdown: remove archives

2009-04-30T18:06:19Z

remove archives

← Older revision		Revision as of 12:06, 30 April 2009
Line 1:		Line 1:
	~~{{archived}}~~
	==Introduction==		==Introduction==

Line 98:		Line 97:

	{{footer}}		{{footer}}
	[[Category:Hosting ~~Archives~~\|htaccess]]		[[Category:Hosting\|htaccess]]

Pashdown: back out header format

2009-04-30T15:57:46Z

back out header format

← Older revision		Revision as of 09:57, 30 April 2009
Line 86:		Line 86:
	'''Note''': This won't have any effect while using a Basic Hosting package.</div>		'''Note''': This won't have any effect while using a Basic Hosting package.</div>

	===Controlling your error page===		==Controlling your error page==

	You can use the ErrorDocument directive to change the 404 error that comes up when someone accesses a bad url on your webspace. The syntax is as follows:		You can use the ErrorDocument directive to change the 404 error that comes up when someone accesses a bad url on your webspace. The syntax is as follows:

Pashdown: back out header format

2009-04-30T15:57:31Z

back out header format

← Older revision		Revision as of 09:57, 30 April 2009
Line 78:		Line 78:


	===Enabling Directory Tree Viewing===		==Enabling Directory Tree Viewing==

	For security reasons, directory tree viewing is disabled by default. If you'd like to show a directory tree of all the files in a specified directory, however, the option is available. You'll need to create a file called ''.htaccess'' in the directory that you want viewable. In your XMission shell, you can do this by issuing the command <pre>echo Options +Indexes > .htaccess</pre> inside the directory you wish to make viewable.		For security reasons, directory tree viewing is disabled by default. If you'd like to show a directory tree of all the files in a specified directory, however, the option is available. You'll need to create a file called ''.htaccess'' in the directory that you want viewable. In your XMission shell, you can do this by issuing the command <pre>echo Options +Indexes > .htaccess</pre> inside the directory you wish to make viewable.
Line 84:		Line 84:
	<div class="messagebox metadata">		<div class="messagebox metadata">

	'''Note''': This won't have any effect while using a Basic Hosting package.</div>		'''Note''': This won't have any effect while using a Basic Hosting package.</div>


	===Controlling your error page===		===Controlling your error page===

Pashdown: format

2009-04-30T15:56:54Z

format

← Older revision		Revision as of 09:56, 30 April 2009
Line 87:		Line 87:


	==Controlling your error page==		===Controlling your error page===

	You can use the ErrorDocument directive to change the 404 error that comes up when someone accesses a bad url on your webspace. The syntax is as follows:		You can use the ErrorDocument directive to change the 404 error that comes up when someone accesses a bad url on your webspace. The syntax is as follows: