Table of Contents
- Introduction
- Installation
- Handling Challenger
- Virtual Servers
- Configuration Examples
- Modules
- Filesystems
- RXML Tags
- Graphics
- Proxy
- Databases
- Miscellaneous Modules
- Security Considerations
- Scripting
- Frontpage
- Upgrading
- Third Party Extensions
- Portability
- Reporting Bugs
- Appendix

  | · Appendix · Available modules · HTTP response codes · Migrating to Challenger

Migrating to Challenger
Challenger can take care of many of the special features of other well-known servers. Basically it is quite painless to switch to Challenger. Below you will find the common special features of other servers and how Challenger treats them.

Image maps

NCSA Image map tip
By adding a redirect from `/your_cgi-bin_dir/imagemap/` to `/`, Challenger will handle all files using the NCSA image map script internally. This means that you will not have to change any links to get your old image maps to work with Challenger.

Server Side Includes
Challenger is compatible with NCSA/Apache style Server Side Includes, SSI. However, we suggest that you rewrite your files to take advantage of Challenger's native features instead, features that can accomplish the same things, but faster, mainly the various RXML commands.

By default, support for the execute script command <doc>`{!--#exec --}`</doc> is turned off, while the others are on. This is controlled in the Main RXML parser.

Server side includes are internally treated like RXML tags.

CGI
All your existing CGI scripts should work but be sure to read the section on the CGI script module.