Apache HTTP Server - Revision history

Sam: Corrected header level

2022-07-13T01:40:03Z

Corrected header level

← Older revision		Revision as of 01:40, 13 July 2022
Line 36:		Line 36:
	* Remember that your browser will throw an error, it is safe to ignore it and add an exception. This will stop future re-occurrence.		* Remember that your browser will throw an error, it is safe to ignore it and add an exception. This will stop future re-occurrence.

	==openSUSE 15.4 specific==		=== openSUSE 15.4 specific ===

	The following line needs editing as follows to allow TLS to function in <code>/etc/sysconfig/apache2</code>:		The following line needs editing as follows to allow TLS to function in <code>/etc/sysconfig/apache2</code>:

Sam: /* HTTPS/TLS */ Added openSUSE 15.4 specific line

2022-07-13T01:39:05Z

HTTPS/TLS: Added openSUSE 15.4 specific line

← Older revision		Revision as of 01:39, 13 July 2022
Line 35:		Line 35:
	* Test your site using https://		* Test your site using https://
	* Remember that your browser will throw an error, it is safe to ignore it and add an exception. This will stop future re-occurrence.		* Remember that your browser will throw an error, it is safe to ignore it and add an exception. This will stop future re-occurrence.

			==openSUSE 15.4 specific==

			The following line needs editing as follows to allow TLS to function in <code>/etc/sysconfig/apache2</code>:
			APACHE_SERVER_FLAGS="SSL HTTP2"

	== HTTP/2 Support ==		== HTTP/2 Support ==

Sam: /* HTTP/2 Support */ Added openSUSE 15.4 specific section

2022-07-13T01:36:00Z

HTTP/2 Support: Added openSUSE 15.4 specific section

← Older revision		Revision as of 01:36, 13 July 2022
Line 53:		Line 53:
	* Open a terminal window		* Open a terminal window
	* Type <code>sudo a2enmod http2</code>. This will enable the built in module in Apache.		* Type <code>sudo a2enmod http2</code>. This will enable the built in module in Apache.
			'''As of at least openSUSE 15.4, the following is already done by default'''
	* Open kwrite and open the file <code>/etc/apache2/httpd.conf</code>		* Open kwrite and open the file <code>/etc/apache2/httpd.conf</code>
	* At the end of the file add the following line:		* At the end of the file add the following line:

Sam: /* HTTP/2 Support */ Added libnghttp2 already installed in later versions

2020-09-08T18:25:47Z

HTTP/2 Support: Added libnghttp2 already installed in later versions

← Older revision		Revision as of 18:25, 8 September 2020
Line 50:		Line 50:
	To enable HTTP/2:		To enable HTTP/2:

	* In the software manager in YaST, you will need to make sure that <code>libnghttp2-14</code> shared library is installed.		* In the software manager in YaST, you will need to make sure that <code>libnghttp2-14</code> shared library is installed (Later versions of openSUSE have this installed already so just check).
	* Open a terminal window		* Open a terminal window
	* Type <code>sudo a2enmod http2</code>. This will enable the built in module in Apache.		* Type <code>sudo a2enmod http2</code>. This will enable the built in module in Apache.

Sam: /* HTTP/2 Support */ Added prefork

2020-09-08T18:24:11Z

HTTP/2 Support: Added prefork

← Older revision		Revision as of 18:24, 8 September 2020
Line 46:		Line 46:
	* You must have a valid TLS certificate setup and working correctly.		* You must have a valid TLS certificate setup and working correctly.
	* You cannot use the prefork method of loading modules into Apache. Consider tabooing the <code>apache-prefork</code> package. The alternatives are worker and event. We are using event. Consequently:		* You cannot use the prefork method of loading modules into Apache. Consider tabooing the <code>apache-prefork</code> package. The alternatives are worker and event. We are using event. Consequently:
	* You cannot use the <code>mod-php7</code> package to load PHP into Apache. PHP-FPM must be configured and used instead. Trying to use it will disable HTTP/2.		* You cannot use the prefork <code>mod-php7</code> package to load PHP into Apache. PHP-FPM must be configured and used instead. Trying to use it will disable HTTP/2.

	To enable HTTP/2:		To enable HTTP/2:

Sam: /* HTTP/2 Support */ Changed part stating prefork method is unavailable.

2020-09-08T18:23:09Z

HTTP/2 Support: Changed part stating prefork method is unavailable.

← Older revision		Revision as of 18:23, 8 September 2020
Line 40:		Line 40:
	Normal websites use HTTP 1.1 which was released in 1999, which is over 2 decades old now; the web has changed a lot since then. Based on Google's SPDY protocol, HTTP/2 allows, amongst other things, native compression, security, concurrent connections and prioritization. This makes the connection much more robust than before.		Normal websites use HTTP 1.1 which was released in 1999, which is over 2 decades old now; the web has changed a lot since then. Based on Google's SPDY protocol, HTTP/2 allows, amongst other things, native compression, security, concurrent connections and prioritization. This makes the connection much more robust than before.

	HTTP/2 is supported with Apache 2.4.12 with the addition of the mod_http2 module. It is natively supported with Apache >2.4.17 ~~without~~ the mod_http2 module. In this article, we will focus on the latter.		HTTP/2 is supported with Apache 2.4.12 with the manual addition of the mod_http2 module. It is natively supported with Apache =>2.4.17 with the mod_http2 module available natively. In this article, we will focus on the latter.

	There are a few prerequisites that are required for HTTP/2 to work:		There are a few prerequisites that are required for HTTP/2 to work:

	* You must have a valid TLS certificate setup and working correctly.		* You must have a valid TLS certificate setup and working correctly.
	* ~~If you~~ are using PHP~~, it~~ must be ~~implemented by the FPM method~~. ~~Using mod_php[x]~~ will disable HTTP/2.		* You cannot use the prefork method of loading modules into Apache. Consider tabooing the <code>apache-prefork</code> package. The alternatives are worker and event. We are using event. Consequently:
			* You cannot use the <code>mod-php7</code> package to load PHP into Apache. PHP-FPM must be configured and used instead. Trying to use it will disable HTTP/2.

	To enable HTTP/2:		To enable HTTP/2:

Sam: /* HTTP/2 Support */ Changed year to decade

2020-09-08T18:17:27Z

HTTP/2 Support: Changed year to decade

← Older revision		Revision as of 18:17, 8 September 2020
Line 38:		Line 38:
	== HTTP/2 Support ==		== HTTP/2 Support ==

	Normal websites use HTTP 1.1 which was released in 1999, ~~17 years ago and~~ the web has changed a lot since then. Based on Google's SPDY protocol, HTTP/2 allows, amongst other things, native compression, security, concurrent connections and prioritization. This makes the connection much more robust than before.		Normal websites use HTTP 1.1 which was released in 1999, which is over 2 decades old now; the web has changed a lot since then. Based on Google's SPDY protocol, HTTP/2 allows, amongst other things, native compression, security, concurrent connections and prioritization. This makes the connection much more robust than before.

	HTTP/2 is supported with Apache 2.4.12 with the addition of the mod_http2 module. It is natively supported with Apache >2.4.17 without the mod_http2 module. In this article, we will focus on the latter.		HTTP/2 is supported with Apache 2.4.12 with the addition of the mod_http2 module. It is natively supported with Apache >2.4.17 without the mod_http2 module. In this article, we will focus on the latter.

Sam: /* Configuring Apache to use your server certificate */Corrected paths as they are directories, removed CSR.

2018-07-30T14:40:04Z

Configuring Apache to use your server certificate: Corrected paths as they are directories, removed CSR.

← Older revision		Revision as of 14:40, 30 July 2018
Line 16:		Line 16:
	* We need to copy the certificates and keys into the correct places. Type the following commands:		* We need to copy the certificates and keys into the correct places. Type the following commands:

	cp key.pem /etc/apache2/ssl.key		cp key.pem /etc/apache2/ssl.key/key.pem
	cp cert.pem /etc/apache2/ssl.crt		cp cert.pem /etc/apache2/ssl.crt/cert.pem
	~~cp csr~~.pem ~~/etc/apache2/ssl.csr~~

	* Close the terminal		* Close the terminal

Sam: Removed localhost link

2018-06-15T03:22:27Z

Removed localhost link

← Older revision		Revision as of 03:22, 15 June 2018
Line 34:		Line 34:
	service apache2 restart		service apache2 restart

	* Test your site ~~by going to~~ https://~~localhost~~		* Test your site using https://
	* Remember that your browser will throw an error, it is safe to ignore it and add an exception. This will stop future re-occurrence.		* Remember that your browser will throw an error, it is safe to ignore it and add an exception. This will stop future re-occurrence.

Sam: /* HTTP/2 Support */ Updated what is needed to support HTTP/2, spell checked

2018-06-15T03:20:33Z

HTTP/2 Support: Updated what is needed to support HTTP/2, spell checked

← Older revision		Revision as of 03:20, 15 June 2018
Line 39:		Line 39:
	== HTTP/2 Support ==		== HTTP/2 Support ==

	Normal websites use HTTP 1.1 which was released in 1999, 17 years ago and the web has changed a lot since then. Based on Google's SPDY protocol, HTTP/2 allows, amongst other things, native compression, security ~~(when implemented with TLS)~~, concurrent connections and ~~prioitization~~. This makes the connection much more robust than before.		Normal websites use HTTP 1.1 which was released in 1999, 17 years ago and the web has changed a lot since then. Based on Google's SPDY protocol, HTTP/2 allows, amongst other things, native compression, security, concurrent connections and prioritization. This makes the connection much more robust than before.

	HTTP/2 is ~~support~~ with Apache 2.4.12 with the addition of the mod_http2 module ~~and~~ is natively supported ~~from~~ Apache 2.4.17 without mod_http2 module. In this article, we will focus on the latter.		HTTP/2 is supported with Apache 2.4.12 with the addition of the mod_http2 module. It is natively supported with Apache >2.4.17 without the mod_http2 module. In this article, we will focus on the latter.

	* In the software manager in YaST, you will need to make sure that <code>~~nghttp2~~</code> is installed.		There are a few prerequisites that are required for HTTP/2 to work:

			* You must have a valid TLS certificate setup and working correctly.
			* If you are using PHP, it must be implemented by the FPM method. Using mod_php[x] will disable HTTP/2.

			To enable HTTP/2:

			* In the software manager in YaST, you will need to make sure that <code>libnghttp2-14</code> shared library is installed.
	* Open a terminal window		* Open a terminal window
	* Type <code>sudo a2enmod http2</code>. This will enable the built in module in Apache.		* Type <code>sudo a2enmod http2</code>. This will enable the built in module in Apache.
	* Open kwrite and open the file <code>/etc/apache2/httpd.conf</code>		* Open kwrite and open the file <code>/etc/apache2/httpd.conf</code>
	* At the end of the file add the following ~~lines~~:		* At the end of the file add the following line:
	Protocols h2 http/1.1		Protocols h2 http/1.1
	~~Protocols h2c http/1.1~~
	* The first line adds support for HTTP/2 over a HTTPS connection and must be used in conjunction with a TLS certificate. This is the default use case. The second line adds support for HTTP/2 over an unencrypted HTTP connection. Not many browsers support this option if at all as it is defined that HTTP/2 is to be used with HTTPS. You may use either or both lines to suit your use case. On this server, only the first line has been enabled.
	* Save the configuration file once you have added your appropriate lines		* Save the configuration file once you have added your appropriate lines
	* Restart Apache by typing <code>sudo service apache2 restart</code>. If you are returned to the command prompt, you have successfully enabled it. You will get an error message and Apache will refuse to start if there is a configuration problem.		* Restart Apache by typing <code>sudo service apache2 restart</code>. If you are returned to the command prompt, you have successfully enabled it. You will get an error message and Apache will refuse to start if there is a configuration problem.