linux web hosting

A module is a piece of code written to the Apache API specifications that is either dynamically-loaded into /www/conf/ httpd.conf, or statically-loaded in the compiled httpsd daemon.

By making these modules available to the Web server using dynamic loading, your Web server can internally process instruction sets rather than relying on external applications such as CGI, increasing the speed at which your Web server responds to requests.

Statically-Linked Modules
The following modules are statically linked in your VPS v2 Virtual Server's Apache.
http_core
apache_ssl
mod_access
mod_actions
mod_alias
mod_auth
mod_auth_dbm
mod_autoindex
mod_cgi
mod_dir
mod_imap
mod_include
mod_log_agent
mod_log_config
mod_log_referrer
mod_mime
mod_setenvif
mod_so.c
mod_userdir

For a description of Apache modules, see:


Dynamically-Loaded Modules
The ability to dynamically load modules is known as "DSO" support. Apache provides for modules to be added dynamically so you do not have to rebuild Apache when you add more functionality.

The /www/libexec directory contains Apache modules that you can add to your Web server dynamically. The modules directory links to libexec.

Most Common Modules
mod_dav (http://www.lyra.org/greg/mod_dav/)
mod_frontpage (ftp://ftp.vr.net/pub/apache/mod_frontpage/)
mod_jserv (http://java.apache.org)
mod_perl (http://perl.apache.org)
mod_php4 (http://www.php.net)
All Other Modules
mod_asis (http://www.apache.org/docs/mod/mod_asis.html)
mod_auth.db (http://www.apache.org/docs/mod/mod_auth_db.html)
mod_auth.msql (http://www.webweaving.org/mod_auth_msql/)
mod_auth.mysql (http://bourbon.netvision.net.il/mysql/mod_auth_mysql/)
mod_auth.pgsql (ftp://ftp.eurolink.it/pub/linux/www/mod_auth_pgsql/)
mod_auth_anon (http://www.apache.org/docs/mod/mod_auth_anon.html)
mod_cern_meta (http://www.apache.org/docs/mod/mod_cern_meta.html)
mod_digest (http://www.apache.org/docs/mod/mod_digest.html)
mod_env (http://www.apache.org/docs/mod/mod_env.html)
mod_expires (http://www.apache.org/docs/mod/mod_expires.html)
mod_fastcgi (http://www.apache.org/docs/mod/mod_fastcgi.html)
mod_headers (http://www.apache.org/docs/mod/mod_headers.html)
mod_info (http://www.apache.org/docs/mod/mod_info.html)
mod_mime_magic (http://www.apache.org/docs/mod/mod_mime_magic.html)
mod_mmap_static (http://www.apache.org/docs/mod/mod_mmap_static.html)
mod_negotiation (http://www.apache.org/docs/mod/mod_negotiation.html)
mod_proxy (http://www.apache.org/docs/mod/mod_proxy.html)
mod_rewrite (http://www.apache.org/docs/mod/mod_rewrite.html)
mod_speling (http://www.apache.org/docs/mod/mod_speling.html)
mod_status (http://www.apache.org/docs/mod/mod_status.html)
mod_usertrack (http://www.apache.org/docs/mod/mod_usertrack.html)
mod_vhost_alias (http://www.apache.org/docs/mod/mod_vhost_alias.html)
Loading Dynamically Loadable Modules
Dynamic modules are loaded into /www/conf/httpd.conf. LoadModule is used at the top of the httpd.conf file so the module loads before any instructions are passed to it.

At the beginning of the httpd.conf file, type:

LoadModule module filename

For more details on the LoadModule command, go to:

The following is an example:

LoadModule env_module modules/mod_env.so

Note: The modules directory is a subdirectory of the ServerRoot directory (/usr/local/apache). The VPS v2 Virtual Server owns the modules directory, but the module files contained in the directory are owned by root. The modules do not count against your VPS v2 Virtual Server quota.

You can load most modules with just the LoadModule command. However, the info and status modules require additional lines in the httpd.conf file.


Loading info_module
To load the info_module:
    1. Go to /www/conf/httpd.conf.
    2. Type the following:
      LoadModule info_module modules/mod_info.so
      <Location /info>
      SetHandler server-info
      </Location>
Loading status_module
To load the status_module:
    1. Go to /www/conf/httpd.conf.
    2. Type the following:
      LoadModule status_module modules/mod_status.so
      <Location /info>
      SetHandler server-info
      </Location>
Using status_module for Your Apache Web Server
Open a browser and go to:
http://www.your_company.com/status/
Refreshing the Status of the Web Server Every 10 Seconds
Open a browser and go to:
http://www.your_company.com/status?refresh=10
Using the info Module
Open a browser and go to:
http://www.your_company.com/info/

This displays Apache Web server information, such as which modules are loaded and other server configuration settings.

If you already have a /status directory or an /info directory, substitute <Location /infoparameter> with whatever location you want. For example, use <Location /apacheinfo> instead. To pull up the info module with the new location, use http://www.your_company.com/apacheinfo/.

Note: Some modules require additional accessing parameters, so be sure to access the URLs listed with the modules for complete documentation.

Compiling Your Own DSO Modules
You can download your own modules and compile them on your Web server. However, be aware that compiling or debugging modules is outside the support limits of Enetrics Communications.

Apache 1.3.11 supports the APXS (Apache extension) tool. APXS allows you to compile and link your own dynamic shared object (DSO) Apache modules. To use APXS, type the following:

% /usr/local/apache/bin/apxs OPTIONS MODULE_CODE

For more information, go to:

Hosting  ::  Web Design  :: Server Administration  ::  Tech Support  ::  Contacts
Data Centers  ::  Tier I Global IP Network  ::  SLA/Contracts  ::  Search  ::  Account Login