With mod_roaming you can use your Apache webserver as a Netscape Roaming Access server. This allows you to store you Netscape Communicator 4.5 preferences, bookmarks, address books, cookies etc. on the server so that you can use (and update) the same settings from any Netscape Communicator 4.5 that can access the server.
Mod_trace_output is an Apache module that is designed to store the data that was sent to a browser, even if the request was for a dynamic page. It is possible to use it to generate statistics on the content viewed by users, and can store captured pages in files or in a MySQL database.
The Archive Webserver will redirect all Web clients to a configurable url such as Google's cached version of your Web pages (provided that it has indexed and cached your pages), or the archived page from the Wayback Machine (www.archive.org). It is intended to be used when your server has crashed, your /home is lost, and you are restoring from a backup but your server is still down.
Load is a utility for Web application and SOAP-based Web services performance and scalability testing. It features a scripting language and a library of test objects for the creation of intelligent agents that drive the Web application or SOAP-based Web service. Running hundreds of agents concurrently shows how your software performs in production environments. Load is a Java application that runs on Linux, Solaris, NT, Win2000, and Macintosh. While Load continues to be maintained, the next generation is the TestMaker program.
FTP Rider is a collection of Python scripts that build an FTP search engine. Only path/filenames are indexed, not the contents of the files. The indexer recursively follows all directories. It indexes multiple FTP servers concurrently (default is 50), and the information is stored in a MySQL database.
mod_auth_cache transparently caches an authentication originally done by a different module. The aim of this module is to speed up complex authentication mechanisms, to reduce database traffic if authenticating thru a backend database, and to implement some sort of authentication reliability if the database server fails. As the caching is completely transparent (done by the webserver), you don't have to change or implement new functions in your existing applications. The module only caches a users authentication and not a users access permissions, which can still be controlled by a different module.