Old configuration:

  Order allow,deny  Deny from all  # Satisfy ALL is the default  Satisfy ALL  Allow from 127.0.0.1  AuthType Basic  PasswdFile %%SYSTEM%%  AuthName secure  Require valid-user

New configuration:

  AuthType Basic  PasswdFile %%SYSTEM%%  AuthName secure  <RequireAll>        Require valid-user        Require ip 127.0.0.1  </RequireAll>

In configurations where both authentication and access control were meaningfully combined, the access control directives should be migrated. This example allows requests meeting either criteria:

  Order allow,deny  Deny from all  Satisfy any  Allow from 127.0.0.1  AuthType Basic  PasswdFile %%SYSTEM%%  AuthName secure  Require valid-user

  AuthType Basic  PasswdFile %%SYSTEM%%  AuthName secure  # Implicitly <RequireAny>  Require valid-user  Require ip 127.0.0.1

New modules

There are some new modules with useful functions in Apache 2.4, below are some basic introduction to some key new modules that currently supported in HTTP server on IBM i 7.2. For more detail information about those modules, refer to IBM i 7.2 IBM Documentation and Apache website.

mod_remoteip

This module is used to treat the user agent which initiated the request as the originating user agent as identified by HTTP Server for the purposes of authorization and logging, even where that user agent is behind a load balancer, front end server, or proxy server.

This module overrides the client IP address for the connection with the user agent IP address reported in the request header configured with the RemoteIPHeader directive.

Once replaced as instructed, this overridden user agent IP address is then used for the mod_authz_host Require ip feature, is recorded by mod_log_config and core %a format strings. The underlying client IP of the connection is available in the %{c}a format string.

mod_buffer

This module provides the ability to buffer the input and output filter stacks. Under certain circumstances, content generators might create content in small chunks. In order to promote memory reuse, in memory chunks are always 8k in size, regardless of the size of the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The addition of a buffer collapses the response into the fewest chunks possible.

When HTTP Server is used in front of an expensive content generator, buffering the response may allow the backend to complete processing and release resources sooner, depending on how the backend is designed.

The buffer filter may be added to either the input or the output filter stacks, as appropriate, using the SetInputFilter, SetOutputFilter, AddOutputFilter or AddOutputFilterByType directives. For example: Using buffer with mod_include

         AddOutputFilterByType INCLUDES;BUFFER text/html

mod_data

This module provides the ability to convert a response into an RFC2397 data URL.

Data URLs can be embedded inline within web pages using something like the mod_include module, to remove the need for clients to make separate connections to fetch what may potentially be many small images. Data URLs may also be included into pages generated by scripting languages such as PHP.

An example of a data URL

data:image/gif;base64,R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAwAAAC8IyPqcvt3wCcDkiLc7C0qwyGHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFzByTB10QgxOR0TqBQejhRNzOfkVJ+5YiUqrXF5Y5lKh/DeuNcP5yLWGsEbtLiOSpa/TPg7JpJHxyendzWTBfX0cxOnKPjgBzi4diinWGdkF8kjdfnycQZXZeYGejmJlZeGl9i2icVqaNVailT6F5iJ90m6mvuTS4OK05M0vDk0Q4XUtwvKOzrcd3iq9uisF81M1OIcR7lEewwcLp7tuNNkM3uNna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PHhhx4dbgYKAAA7

The filter takes no parameters, and can be added to the filter stack using the SetOutputFilter directive, or any of the directives supported by the mod_filter module.

For example:

<Location /data/images>

            SetOutputFilter DATA

</Location>

mod_ratelimit

This module provides a filter named RATE_LIMIT to limit client bandwidth. The connection speed to be simulated is specified, in KiB/s, using the environment variable rate-limit.

For example:

<Location /downloads>

            SetOutputFilter RATE_LIMIT

            SetEnv rate-limit 400

</Location>

mod_request

This module provides filters to handle and make available HTTP request bodies

Under normal circumstances, request handlers such as the default handler for static files will discard the request body when it is not needed by the request handler.

When directive KeptBodySize has a value greater than zero, request handlers that would otherwise discard request bodies will instead set the request body aside for use by filters up to the maximum size specified.

This feature makes it possible to break up complex web pages and web applications into small individual components, and combine the components and the surrounding web page structure together using mod_include. The components can take the form of CGI programs, scripted languages, or URLs reverse proxied into the URL space from another server using mod_proxy.

If the request size sent by the client exceeds the maximum size allocated by the KeptBodySize directive, the server will return 413 Request Entity Too Large.

mod_reflector

This module provides Reflection of a request body as a response via the output filter stack.

This module allows request bodies to be reflected back to the client, in the process passing the request through the output filter stack. A suitably configured chain of filters can be used to transform the request into a response. This module can be used to turn an output filter into an HTTP service.

For example,

Pass the request body through the DEFLATE filter to compress the body. This request requires a Content-Encoding request header containing "gzip" for the filter to return compressed data.

<Location /compress>

            SetHandler reflector

            SetOutputFilter DEFLATE

</Location>

mod_reqtimeout

This module sets timeout and minimum data rate for receiving requests.

The new RequestReadTimeout directive can set various timeouts for receiving the request headers and the request body from the client. If the client fails to send headers or body within the configured time, a 408 REQUEST timeout error is sent.

Examples