Extending IBM HTTP Server functionality with third-party plug-in modules
This section contains topics on using third-party plug-in modules with IBM® HTTP Server.
Before you begin
- The openssl library cannot be loaded by IBM HTTP Server plug-in modules.
- Plug-in modules provided by IBM may use the Global Security Kit (GSKit) library for SSL communications. These plug-in modules must comply with the GSKit restrictions for using a local GSKit installation to interoperate with the current release of IBM HTTP Server.
About this task
Important: The use of third-party plug-in
modules
does not prevent IBM HTTP Server from being supported, but IBM cannot
support
the third-party plug-in module itself. If a problem occurs when the
third-party
plug-in module is loaded, IBM support might ask for the problem
to be reproduced
without the third-party plug-in module loaded, in order to determine
if the
problem is specific to the configuration with the third-party plug-in
module.
If a problem is specific to the configuration with the third-party
plug-in
module, the provider of that module might need to help determine the
cause
of the problem. IBM cannot
resolve such problems without the involvement of the provider of the
module,
as this requires understanding of the implementation of the module,
particularly
with regard to its use of the Apache APIs.
Procedure
- Identify viable compilers.
Apache and third-party plug-in module testing incorporated the compilers and compiler levels that are listed in this topic.
-
Determine the method to use to build the dynamic
modules. Two common options for building dynamic modules are described in this topic.
- Considerations for
building dynamic modules. Restrictions apply when building a module to run with IBM HTTP Server. This topic describes the restrictions.