While it's possible to build the Apache Server for OS/2 yourself, doing so requires you to download and install a whole swag of GNU utilities as well as EMX GCC. If you really want to do this see Building Apache for OS/2

With the release of Apache Server v1.3.9, loadable modules are now supported in OS/2 which means that there is no longer any need for multiple binaries compiled with different sets of modules. You just have to edit your httpd.conf file to load the modules you want at run time

The normal Apache OS/2 binary distribution contains all the standard modules. You can also load third party modules as they become available

Also available is Apache HTTP Server v2.0 which was released for general availability on the 5th April 2002

Other items of interest to Apache for OS/2 users
• Builds of PHP3 & PHP4 in a number of configurations

• A simpleutility for doing command line restart or shutdown of a running server

• A version of htpasswd modified to use GDBM for making password files usable by mod_auth_dbm, htpasswd_gdbm
• Mod_Rexx from IBM Developer Works "brings the full power of the REXX language processor of your choice (IBM Object REXX, Regina REXX, etc.) to the Apache web page developer. Mod_Rexx can be used as a dynamic web page creation tool or to process any part of an Apache request."

While I've done much of the hard work by getting the thing compiled, installation is still not going to be a no-brainer. Please don't send me any questions on configuring Apache. The Apache distribution includes a manual which should be the place you go if you have questions

• You need to have the emx run time library installed. Get emxrt.zip and add appropriate entries to your PATH & LIBPATH (described in emxrt.doc). Make sure you have at least v0.9d fix 3, and add " " to your config.sys or apache start up script. This increases the number of file handles and activates a workaround for a file handle leak

• The default directory to run from is pache so if you run from anywhere else you need to use a -f or -d switch as in
• Use lower case and forward slashesfor all path and file names in the config files


• To use interpreted script languages like perl for CGI you should include a line that looks like this as the first line of your script and ensure that perl.exe is on your path. Alternatively you can specify the full path of the interpreter in the #! line

• To use Object Rexx for CGI scripts you'll need to add to your httpd.conf

• If your CGI (any type) does any DNS queries you'll need to add to your httpd.conf.