Apache2 Http Server



This chapter describes how to install and configure the Apache HTTP Server plug-in. It contains the following sections:

  1. HTTPD - Apache2 Web Server Apache is the most commonly used Web server on Linux systems. Web servers are used to serve Web pages requested by client computers. Clients typically request and view Web pages using Web browser applications such as Firefox, Opera, Chromium, or Internet Explorer.
  2. Set up an Apache web server on an EC2 instance. Set up an Apache web server on multiple EC2 instances by creating an Auto Scaling group. You can create multiple EC2 instances using Amazon EC2 Auto Scaling, an AWS service that allows you to increase or decrease the number of EC2 instances in a group according to your application needs.
Tutorial

Note:

For proxying requests from Oracle HTTP Server to Oracle WebLogic Server, use the mod_wl_ohs plug-in, which is similar to the plug-in for Apache HTTP Server, but need not be downloaded and installed separately. For information about configuring mod_wl_ohs, see Chapter 2, 'Configuring the mod_wl_ohs Plug-In for Oracle HTTP Server.'.

4.1 Install the Apache HTTP Server Plug-In

After you download the Apache HTTP Server plug-in as described in Section 1.2, 'Availability of Version 1.1 Plug-Ins,', you can install it as an Apache HTTP Server module in your Apache HTTP Server installation.

Although the Apache2 web server is configured by default to host one website, you can use it to host multiple web sites/applications using the concept of “ Virtual Host ”. Therefore Virtual Host is a term that refers to the practice of running more than one web site/application (such as example.com and example1.com) on a single server. What is Apache2 Web Server? Apache is the most commonly used Web server on Linux systems. Web servers are used to serve Web pages requested by client computers. Clients typically request and view. I am trying to create a web server on my ubuntu 18.04 so i installed Apache2 but i can't start it. Here's what appeared when i run the systemctl status apache2.service command apache2.service.

4.1.1 Installation Prerequisites

Before you install the Apache HTTP Server plug-in, do the following:

  • Download the Apache HTTP Server plug-in, as described in Section 1.2, 'Availability of Version 1.1 Plug-Ins.'

  • Extract the plug-ins zip distribution to the location of your choice on the target system; for example, /home/myhome/weblogic-plugins-1.1/.

  • Install JDK 6 if you want to use SSL. The JDK 6 installation is required to use the orapki utility, which manages public key infrastructure (PKI) elements, such as wallets and certificate revocation lists, for use with SSL.

  • Make sure that you have a supported Apache HTTP Server installation.

    For more information, see:

    http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html.

  • Make sure that a supported version of Oracle WebLogic Server is configured and running on a target system. However, it does not need to be running on the system on which you extracted the plug-in zip distribution. For the supported Oracle WebLogic Server versions, see:

    http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html.

4.1.2 Installing the Apache HTTP Server Plug-In

The Apache HTTP Server plug-in is distributed as a shared object (.so) for Unix platforms and a DLL for Windows.

To install the Apache HTTP Server plug-in:

  1. Make sure that the weblogic-plugins-1.1/lib folder is included in LD_LIBRARY_PATH on Unix systems (and PATH on Windows systems). If you do not do this, you see linkage errors when starting Apache HTTP Server.

  2. In the location where you unzipped the downloaded plug-in file, locate lib/mod_wl.so, or libmod_wl.dll for windows; for example, /home/myhome/weblogic-plugins-1.1/lib/mod_wl.so.

  3. Verify that the mod_so.c module is enabled.

    If you installed Apache HTTP Server using the script supplied by Apache, mod_so.c is already enabled. Verify that mod_so.c is enabled by executing the following command:

    • Windows

    • UNIX/Linux

    (APACHE_HOME is the directory that contains the Apache HTTP Server installation.)

    This command lists all enabled modules. If mod_so.c is not listed, you must rebuild your Apache HTTP Server, making sure that the following configure option is specified:

  4. Make a copy of the APACHE_HOME/bin/httpd.conf file for backup.

  5. Open the httpd.conf file.

  6. Install the Apache HTTP Server plug-in module for Apache 2.2.x by adding the following line. For Windows, specify the .dll file.

  7. Verify the syntax of the httpd.conf file by running the following command:

    • Windows

    • UNIX/Linux

    If the httpd.conf file contains any errors, the output of this command shows the errors; otherwise, the command returns the following:

4.2 Configure the Apache HTTP Server Plug-In

This section describes how to edit the httpd.conf file to proxy requests by path or by MIME type, to enable HTTP tunneling, and to use other Oracle WebLogic Server plug-in parameters.

4.2.1 Editing the httpd.conf File

Edit the httpd.conf file in your Apache HTTP Server installation to configure the Apache HTTP Server plug-in.

  1. Open the httpd.conf file, if it is not already open.

  2. To proxy requests by MIME type, add an IfModule block that defines one of the following:

    • For a non-clustered WebLogic Server: the WebLogicHost and WebLogicPort parameters.

    • For a cluster of WebLogic Servers: the WebLogicCluster parameter.

    Example:

  3. To proxy requests by MIME type, add a MatchExpression line to the IfModule block. Note that if both MIME type and proxying by path are enabled, proxying by path takes precedence over proxying by MIME type.

    For example, the following IfModule block for a non-clustered WebLogic Server specifies that all files with MIME type .jsp are proxied:

    You can also use multiple MatchExpressions, for example:

    If you are proxying requests by MIME type to a cluster of WebLogic Servers, use the WebLogicCluster parameter instead of the WebLogicHost and WebLogicPort parameters. For example:

  4. To proxy requests by path, use the Location block and the SetHandler statement. SetHandler specifies the handler for the Apache HTTP Server plug-in module. For example the following Location block proxies all requests containing /weblogic in the URL:

    The PathTrim parameter specifies a string trimmed from the beginning of the URL before the request is passed to the WebLogic Server instance (see Section 7.1, 'General Parameters for Web Server Plug-Ins').

  5. The PathTrim parameter must be configured inside the <Location> tag. These known issues arise when you configure the Apache plug-in to use SSL

    • The following configuration is incorrect:

      The following configuration is the correct setup:

    • The current implementation of the WebLogic Server Apache plug-in does not support the use of multiple certificate files with Apache SSL.

  6. Optionally, enable HTTP tunneling for t3 or IIOP.

    1. To enable HTTP tunneling if you are using the t3 protocol and weblogic.jar, add the following Location block to the httpd.conf file:

    2. To enable HTTP tunneling if you are using the IIOP, the only protocol used by the WebLogic Server thin client, wlclient.jar, add the following Location block to the httpd.conf file:

  7. Define any additional parameters for the Apache HTTP Server plug-in.

    The Apache HTTP Server plug-in recognizes the parameters listed in Section 7.1, 'General Parameters for Web Server Plug-Ins'. To modify the behavior of your Apache HTTP Server plug-in, define these parameters either:

    • In a Location block, for parameters that apply to proxying by path, or

    • At global or virtual host scope, for parameters that apply to proxying by MIME type.

  8. Verify the syntax of the httpd.conf file by running the following command:

    • Windows

    • UNIX/Linux

    If the httpd.conf file contains any errors, the output of this command shows the errors; otherwise, the command returns the following:

  9. Start the Apache HTTP Server.

    • Windows

    • UNIX/Linux

  10. Send a request to http://apache-host:apache-port/mywebapp/my.jsp from the browser. Validate the response.

4.2.1.1 Placing WebLogic Properties Inside Location or VirtualHost Blocks

Apache Windows Download

If you choose to not use the IfModule, you can instead directly place the WebLogic properties inside Location or VirtualHost blocks. Consider the following examples of the Location and VirtualHost blocks:

4.2.2 Including a weblogic.conf File in the httpd.conf File

If you want to keep several separate configuration files, you can define parameters in a separate configuration file called weblogic.conf file, by using the Apache HTTP Server Include directive in an IfModule block in the httpd.conf file:

The syntax of weblogic.conf files is the same as that for the httpd.conf file.

Exploit

This section describes how to create weblogic.conf files, and includes sample weblogic.conf files.

4.2.2.1 Creating weblogic.conf Files

Be aware of the following when constructing a weblogic.conf file.

  • Enter each parameter on a new line. Do not put '=' between a parameter and its value. For example:

  • If a request matches both a MIME type specified in a MatchExpression in an IfModule block and a path specified in a Location block, the behavior specified by the Location block takes precedence.

  • If you use an Apache HTTP Server <VirtualHost> block, you must include all configuration parameters (MatchExpression, for example) for the virtual host within the <VirtualHost> block (see Apache Virtual Host documentation at http://httpd.apache.org/docs/vhosts/).

  • If you want to have only one log file for all the virtual hosts configured in your environment, you can achieve it using global properties. Instead of specifying the same Debug, WLLogFile and WLTempDir properties in each virtual host you can specify them just once in the <IfModule> tag.

  • Sample httpd.conf file:

  • All the requests which match /jurl/* will have Debug Level set to ALL and log messages will be logged to c:/tmp/global_proxy.log file. All the requests which match /web/* will have Debug Level set to OFF and no log messages will be logged. All the requests which match /foo/* will have Debug Level set to ERR and log messages will be logged to c:/tmp/foo_proxy.log file.

  • Oracle recommends that you use the MatchExpression statement instead of the <Files> block.

4.2.2.2 Sample weblogic.conf Configuration Files

The following examples of weblogic.conf files may be used as templates that you can modify to suit your environment and server. Lines beginning with # are comments.

In Example 4-2, the MatchExpression parameter syntax for expressing the filename pattern, the WebLogic Server host to which HTTP requests should be forwarded, and various other parameters is as follows:

The first MatchExpression parameter below specifies the filename pattern *.jsp, and then names the single WebLogicHost. The paramName=value combinations following the pipe symbol specify the port at which WebLogic Server is listening for connection requests, and also activate the Debug option. The second MatchExpression specifies the filename pattern *.http and identifies the WebLogicCluster hosts and their ports. The paramName=value combination following the pipe symbol specifies the error page for the cluster.

Example 4-2 Example Using Multiple WebLogic Clusters

Example 4-3 shows an example without WebLogic clusters.

Example 4-4 shows an example of configuring multiple name-based virtual hosts.

Example 4-4 Example Configuring Multiple Name-Based Virtual Hosts

You must define a unique value for ServerName or some plug-in parameters will not work as expected.

4.2.2.3 Template for the Apache HTTP Server httpd.conf File

This section contains a sample httpd.conf file for Apache 2.2. You can use this sample as a template and modify it to suit your environment and server. Lines beginning with # are comments.

Note that Apache HTTP Server is not case sensitive.

Apache Http Server Benchmarking Tool

Webmasters and students may want to learn how to redirect an old domain to a new one or one sub-domain to another or HTTP to HTTPS… For example, with Apache2 redirect modules, one can redirect http//example.net to http://example.com or http://www.example.com to http://example.com or http://example.com to https://example.com…

This brief tutorial is going to show students and new users how to set up Apache2 directs easily… the method below can also be used with switching your HTTP domain to HTTPS…

When you’re ready to configure Apache2 directs, continue below:

Step 1: Install / Configure Apache2 HTTPS

To configure Apache2 to redirect all traffic to HTTPS, you must configure and enable its SSL modules.. The post below shows you how to install and configure Apache2 to communicate over HTTPS… however, both HTTP and HTTPS are enabled… the method below will show you how to redirect all traffic to the server to use HTTPS only..

Step 2: Redirect Apache2 HTTP to HTTPS

Our post above set up Apache2 to communicate over both HTTP and HTTPS… however, in today’s environment, it’s recommended to choose one type of protocol and redirect the other to it..

For example, you should redirect all HTTP (80) to HTTPS (443). To do that, add the highlighted portion of the code to your Apache2 site configuration file…

Run the commands below to open Apache2 default site configuration file..

sudo nano /etc/apache2/sites-available/000-default.conf

Then add the highlighted portion to the bottom of the file.

Redirect to same domain on HTTPS only

The configuration above redirect all requests to use HTTPS only to communicate with the server with domain name example.com. So, http://example.com and http://www.example.com will be redirect to https://example.com

Step 3: Redirect Old Domain to New

If you want to redirect from an old domain to a new one, the setting below should help you do that… For this setup, HTTPS isn’t required… Run the commands below to open Apache2 default site configuration file.

sudo nano /etc/apache2/sites-available/000-default.conf

Then add the highlighted portion to the bottom of the file.

Apache Http Server Tutorial

Redirect old domain to new domain

The above code added to your Apache2 site configuration file will redirect an old domain to a new one without HTTPS…. the highlighted code above redirects http://example.net and http://www.example.net to http://example.com

Apache Http Server Api

After making the changes above, run the commands below to test your settings and enable Apache2 rewrite and SSL modules.

If you don’t see any error messages then you’re good. Restart Apache2 web server by running the commands below.

sudo systemctl restart apache2.service

That’s it! This is how to configure Apache2 HTTP 301 redirects

~Enjoy~

Apache Http Server Has Stopped Working

You may also like the post below: