Apache - Revision history

Admin at 22:00, 25 March 2017

2017-03-25T22:00:14Z

← Older revision		Revision as of 22:00, 25 March 2017
Line 321:		Line 321:

	[[Category:Apache]]		[[Category:Apache]]

			[[Category:Server]]

Admin: /* Mac Leopard (OS X 10.5) */

2017-03-25T21:04:55Z

Mac Leopard (OS X 10.5)

← Older revision		Revision as of 21:04, 25 March 2017
Line 30:		Line 30:
	I configured Apache on Mac Leopard with the following configure line:		I configured Apache on Mac Leopard with the following configure line:

	<~~source lang="bash"~~>		<pre>
	./configure \		./configure \
	--prefix=/path/to/apache \		--prefix=/path/to/apache \
Line 36:		Line 36:
	--enable-mods-shared="all ssl cache proxy authn_alias mem_cache file_cache		--enable-mods-shared="all ssl cache proxy authn_alias mem_cache file_cache
	charset_lite dav_lock disk_cache mod_dav mod_dav_svn"		charset_lite dav_lock disk_cache mod_dav mod_dav_svn"
	</~~source~~>		</pre>

	===Mac Snow Leopard (OS X 10.6)===		===Mac Snow Leopard (OS X 10.6)===

Admin: /* PHP Module */

2017-03-25T21:04:42Z

PHP Module

← Older revision		Revision as of 21:04, 25 March 2017
Line 144:		Line 144:
	Once the PHP module has been added to the Apache configuration file, you will also have to add a few other things to your <code>httpd.conf</code>:		Once the PHP module has been added to the Apache configuration file, you will also have to add a few other things to your <code>httpd.conf</code>:

	<~~syntaxhighlight lang="apache"~~>		<pre>
	AddHandler php5-script php # <-- This line should be added automatically by PHP		AddHandler php5-script php # <-- This line should be added automatically by PHP

Line 159:		Line 159:
	</IfModule>		</IfModule>

	</~~syntaxhighlight~~>		</pre>

	== SVN Module ==		== SVN Module ==

Admin: /* Protecting Directories with .htaccess */

2017-03-25T21:04:26Z

Protecting Directories with .htaccess

← Older revision		Revision as of 21:04, 25 March 2017
Line 204:		Line 204:
	To password-protect a directory, the .htaccess file will need to contain information about where the valid usernames and passwords are stored.		To password-protect a directory, the .htaccess file will need to contain information about where the valid usernames and passwords are stored.

	<~~syntaxhighlight lang="apache"~~>		<pre>
	AuthUserFile /path/to/.htpasswd		AuthUserFile /path/to/.htpasswd
	AuthType Basic		AuthType Basic
	AuthName "This is a login message"		AuthName "This is a login message"
	</~~syntaxhighlight~~>		</pre>

	The .htaccess file points to an .htpasswd file containing valid usernames and passwords. This .htpasswd file ''should not be in the web root.'' It should only be accessible via SSH (or, at most, by FTP). Also, if you don't like the name ".htpasswd", you can call it whatever you want, as long as your .htaccess is accurate. However, .htpasswd is the traditional naming convention.		The .htaccess file points to an .htpasswd file containing valid usernames and passwords. This .htpasswd file ''should not be in the web root.'' It should only be accessible via SSH (or, at most, by FTP). Also, if you don't like the name ".htpasswd", you can call it whatever you want, as long as your .htaccess is accurate. However, .htpasswd is the traditional naming convention.
Line 214:		Line 214:
	If we want to allow any user in the .htpasswd file, we can add the line		If we want to allow any user in the .htpasswd file, we can add the line

	<~~syntaxhighlight lang="apache"~~>		<pre>
	require valid-user		require valid-user
	</~~syntaxhighlight~~>		</pre>

	Otherwise, we can specify that only certain users are allowed access:		Otherwise, we can specify that only certain users are allowed access:

	<~~syntaxhighlight lang="apache"~~>		<pre>
	require user charles		require user charles
	</~~syntaxhighlight~~>		</pre>

	Being able to set authorization settings in an .htaccess file requires the Apache server has the following directive set in httpd.conf:		Being able to set authorization settings in an .htaccess file requires the Apache server has the following directive set in httpd.conf:

	<~~syntaxhighlight lang="apache"~~>		<pre>
	AllowOverride AuthConfig		AllowOverride AuthConfig
	</~~syntaxhighlight~~>		</pre>



	== Protecting Directories with httpd.conf ==		== Protecting Directories with httpd.conf ==

Admin: /* Protecting Directories with httpd.conf */

2017-03-25T20:30:06Z

Protecting Directories with httpd.conf

← Older revision		Revision as of 20:30, 25 March 2017
Line 240:		Line 240:
	In your <code>httpd.conf</code> apache configuration file, you can specify configuration settings for the entire server. However, you can also include directory-specific configuration settings, by putting them in a <code><Directory></code> block:		In your <code>httpd.conf</code> apache configuration file, you can specify configuration settings for the entire server. However, you can also include directory-specific configuration settings, by putting them in a <code><Directory></code> block:

	<~~syntaxhighlight lang="apache"~~>		<pre>
	<Directory /path/to/apache/htdocs/secret>		<Directory /path/to/apache/htdocs/secret>
	# Directory-specific configurations go here		# Directory-specific configurations go here
	</Directory>		</Directory>
	</~~syntaxhighlight~~>		</pre>

	Next, the same stuff that went into the .htaccess files (above section) can go into the <code><Directory></code> block:		Next, the same stuff that went into the .htaccess files (above section) can go into the <code><Directory></code> block:

	<~~syntaxhighlight lang="apache"~~>		<pre>
	<Directory /path/to/apache/htdocs/secret>		<Directory /path/to/apache/htdocs/secret>
	AuthType Basic		AuthType Basic
Line 257:		Line 257:
	#Require user charles		#Require user charles
	</Directory>		</Directory>
	</~~syntaxhighlight~~>		</pre>

	Also see the (somewhat skimpy) [http://httpd.apache.org/docs/2.0/mod/mod_auth.html Mod Auth documentation]		Also see the (somewhat skimpy) [http://httpd.apache.org/docs/2.0/mod/mod_auth.html Mod Auth documentation]
Line 267:		Line 267:
	For example, to allow only users from 127.0.0.1 (that is, just yourself):		For example, to allow only users from 127.0.0.1 (that is, just yourself):

	<~~syntaxhighlight lang="apache"~~>		<pre>
	<Directory /path/to/apache/htdocs/secret>		<Directory /path/to/apache/htdocs/secret>
	Order deny,allow # <-- Specifies the order in which to apply the filters (deny filters first, then allow filters)		Order deny,allow # <-- Specifies the order in which to apply the filters (deny filters first, then allow filters)
Line 273:		Line 273:
	Allow from 127.0.0.1		Allow from 127.0.0.1
	</Directory>		</Directory>
	</~~syntaxhighlight~~>		</pre>

	To deny users from 127.0.0.1 (uh, yeah, suuuuure):		To deny users from 127.0.0.1 (uh, yeah, suuuuure):

	<~~syntaxhighlight lang="apache"~~>		<pre>
	<Directory /path/to/apache/htdocs/secret>		<Directory /path/to/apache/htdocs/secret>
	Deny from 127.0.0.1		Deny from 127.0.0.1
	</Directory>		</Directory>
	</~~syntaxhighlight~~>		</pre>

	In order for Apache to understand these <code>Auth</code> directives, the Auth module has to be turned on.		In order for Apache to understand these <code>Auth</code> directives, the Auth module has to be turned on.

Admin: /* Using htpasswd */

2017-03-25T20:29:28Z

Using htpasswd

← Older revision		Revision as of 20:29, 25 March 2017
Line 297:		Line 297:
	To create a .htpasswd file for the first time, you'll call the htpasswd program from the command line and use the <code>-c</code> flag:		To create a .htpasswd file for the first time, you'll call the htpasswd program from the command line and use the <code>-c</code> flag:

	<~~syntaxhighlight~~>		<pre>
	htpasswd -c /path/to/.htpasswd charles		htpasswd -c /path/to/.htpasswd charles
	</~~syntaxhighlight~~>		</pre>

	This will prompt me to enter a password, will hash the password, and will store both in the file in the form <code>username:*******</code> (where <code>******</code> is the hashed password).		This will prompt me to enter a password, will hash the password, and will store both in the file in the form <code>username:*******</code> (where <code>******</code> is the hashed password).
Line 305:		Line 305:
	To create a username and password combination in an existing .htpasswd file,		To create a username and password combination in an existing .htpasswd file,

	<~~syntaxhighlight~~>		<pre>
	htpasswd /path/to/.htpasswd charles		htpasswd /path/to/.htpasswd charles
	</~~syntaxhighlight~~>		</pre>

	Alternatively, you can specify a password on the command line (but be aware that someone could look through your history and find it):		Alternatively, you can specify a password on the command line (but be aware that someone could look through your history and find it):

	<~~syntaxhighlight~~>		<pre>
	htpasswd /path/to/.htpasswd charles MySecretPassword		htpasswd /path/to/.htpasswd charles MySecretPassword
	</~~syntaxhighlight~~>		</pre>

	You can visit the above link to the Apache website for more details.		You can visit the above link to the Apache website for more details.


	=Flags=		=Flags=

Admin: /* Using htpasswd */

2017-03-25T19:55:18Z

Using htpasswd

← Older revision		Revision as of 19:55, 25 March 2017
Line 318:		Line 318:


			=Flags=

	{{Programs}}		{{Programs}}
	{{Unix Programs}}		{{Unix Programs}}

			[[Category:Apache]]

Admin: /* SSL Module */

2017-03-25T19:42:11Z

SSL Module

← Older revision		Revision as of 19:42, 25 March 2017
Line 175:		Line 175:
	== SSL Module ==		== SSL Module ==

	~~Also see [[~~Apache/~~SSL]]~~		SSL, secure socket layer, provides a secure way of communicating private information between a client, using their web browser, and the web server, running Apache. It allows you to serve HTTPS pages, which requires an SSL certificate (public/private key) that allows people to trust their connection to your server is genuine and secure.

	~~SSL, secure socket layer, provides a secure way of communicating private information between a client, using their web browser, and~~ the ~~web server, running~~ Apache.		Covered on the [[Apache/SSL]] page.

	~~To create secure Apache web sites, which are prefixed with <code>https:~~/~~/</code>, you can use the <code>mod_ssl</code> module, documented here: http://httpd.apache.org/docs/2.0/ssl/~~

	~~In order to use <code>mod_ssl</code>, you need to install [http://www.openssl.org/ OpenSSL~~] ~~and configure with the arguments <code>--enable-ssl --with-ssl=/path/to/open/ssl</code>. You can set a whole bunch of different options, documented here: http://www.openssl.org/~~

	You will need to sign your own certificate, since a signed SSL certificate will set you back a couple thousand dollars a year. This will cause all users using the Apache SSL webpage to see a warning, but that's a small price to pay, compared with the cost of a signed SSL certificate.

	== Other Interesting Apache Modules ==		== Other Interesting Apache Modules ==

Admin: /* SSL Module */

2017-03-25T19:40:57Z

SSL Module

← Older revision		Revision as of 19:40, 25 March 2017
Line 175:		Line 175:
	== SSL Module ==		== SSL Module ==

	Also see [[SSL]]		Also see [[Apache/SSL]]

	SSL, secure socket layer, provides a secure way of communicating private information between a client, using their web browser, and the web server, running Apache.		SSL, secure socket layer, provides a secure way of communicating private information between a client, using their web browser, and the web server, running Apache.

Admin: /* SSL Module */

2017-03-25T19:40:20Z

SSL Module

← Older revision		Revision as of 19:40, 25 March 2017
Line 174:		Line 174:

	== SSL Module ==		== SSL Module ==

			Also see [[SSL]]

	SSL, secure socket layer, provides a secure way of communicating private information between a client, using their web browser, and the web server, running Apache.		SSL, secure socket layer, provides a secure way of communicating private information between a client, using their web browser, and the web server, running Apache.