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

  | · Introduction · Is It Really a Bug? · Necessary Information · How to report

- Appendix

Introduction
We are committed to make Challenger a software of high quality that does not cause problems for its users. For us to reach that goal it is important that we get reports about bugs encountered while using the software.

For a report to be useful it must give us enough information to pin-point the problem. If we don't understand what the problem is, it is hard to fix it. Before sending any bug report, you should read the bug report critically and think whether you would be able to reproduce the bug with the information in the bug report. If you can't, we probably can't either.

Idonex does not provide free support for our products. We will use your input to help fix bugs and improve the quality of our manuals, but we will not be able to reply to all bug reports. It is better to post questions on the Roxen Challenger mailinglist where Challenger users probably will help you.