Directives no longer supported on HTTP Server (powered by Apache)

This topic provides information about what directives are no longer supported by HTTP Server (powered by Apache).

Important: Information for this topic supports the latest PTF levels for HTTP Server for i5/OS . It is recommended that you install the latest PTFs to upgrade to the latest level of the HTTP Server for i5/OS. Some of the topics documented here are not available prior to this update. See http://www.ibm.com/servers/eserver/iseries/software/http/services/service.htm Link outside Information Center for more information.

The following directives are no longer supported on HTTP Server (powered by Apache).

Directives

AddModule

Module: core
Syntax: AddModule module [module ...]
Default: none
Context: server config
Override: none
Origin: Apache
Example: AddModule mod_cgi

The AddModule directive allows the server to activate specific modules in the server after a ClearModuleList has been performed. The server comes with a pre-loaded list of active modules. Only those modules are valid. A list of valid modules can be obtained using the '-l' option on the command line. The example above would activate the module mod_cgi. If this module is already active then the directive will be ignored.

Parameter: module
  • Module is any valid module in the pre-loaded list that came with the HTTP Server.

See also ClearModuleList.

ClearModuleList

Module: core
Syntax: ClearModuleList
Default: none
Context: server config
Override: none
Origin: Apache
Example: ClearModuleList

The ClearModuleList directive will clear the built-in list of active modules provided by the server. To reactivate this module list use the AddModule directive.

IconPath

Module: mod_auto_index
Syntax: IconPath
Default: IconPath /icons
Context: server config, virtual host, directory, .htaccess
Override: none
Origin: iSeries™
Example: IconPath /myicons/small/

The IconPath directive to specify URL information to be added at the beginning of each icon-URL specified on the following directives:

The value that you specify on this directive is added to the icon-URL value on each of the other directives to form the full request URL for each icon. The following path and directory is the default location for icons:

/QIBM/ProdData/HTTPA/icons

Special Usage Considerations:

For example, a configuration containing:

Alias /icons/small /QIBM/ProdData/HTTPA/icons/small
IconPath /icons/small/
AddIcon blank.gif ^^BLANKICON^^

This causes the server to generate a request for the directory list icon as /icons/small/blank.gif. The server uses the alias directive to resolve the request to the proper file. This is different from Apache than on other platforms.

On another platform you would use:

Alias /icons /full/icon/path
AddIcon /icons/blank.gif ^^BLANKICON^^

IconPath is an iSeries specific directive for Apache; therefore, precautions must be taken if the Apache configuration file is modified manually. On the iSeries, you would use:

Alias /icons /QIBM/ProdData/HTTPA/icons
AddIcon blank.gif ^^BLANKICON^^

Since IconPath is set to /icons/ by default, it will be prepended to 'blank.gif' when the AddIcon directive is used.

Port

Module: core
Syntax: Port number
Default: Port 80
Context: server config
Override: none
Origin: Apache
Example: Port 8080

The Port directive has two behaviors:

In no event does a Port setting affect what ports a VirtualHost responds on, the VirtualHost directive itself is used for that. The primary behavior of Port should be considered to be similar to that of the ServerName directive. The ServerName and Port together specify what you consider to be the canonical address of the server. (See also UseCanonicalName.)

Parameter: number
  • Where number is a number from 0 to 65535; some port number (especially below 1024) are reserved for particular protocols. The standard port for http protocol is 80.
Note: The Listen directive is used as an alterative to Port.