FAQ

OpenSA web server Frequently Asked Questions

$Revision: 1.2 $ ($Date: 2003/02/14 17:57:23 $)
Written by: $Author: dsr $

The latest version of this FAQ is always available from the main OpenSA web site, at http://www.opensa.org/manual/faq/.

If you are reading a text-only version of this FAQ, you may find numbers enclosed in brackets (such as "[12]"). These refer to the list of reference URL's to be found at the end of the document. These references do not appear, and are not needed, for the hypertext version.

The Questions

Background
General information
Update information
1. How do i update to a new beta release?
2. How do i update to a new final release?
Supporting OpenSA
1. Can I help in writing docs etc.?
2. Can I help in development of OpenSA?

The Answers

A. Background

What is the OpenSA web server?
The OpenSA web server
- is a powerful, flexible, HTTP/1.1 compliant web server
- is based on the Apache httpd server
- is highly configurable and extensible with third-party modules
- falls under Open-Source software (BSD-style license)
- is useable for both commercial and non-commercial use
- is prepared to run on the Win32 (Windows 95/98/NT/2000) platform
- is actively being developed
- encourages user feedback through new ideas, bug reports and patches
- has full User and Developer Support
- is always based on current Apache versions
How and why was OpenSA created?
The Project Introduction document explains how the OpenSA project evolved from its beginnings as an usability project to its current status as one of the fastest, most efficient, and most functional web servers derivates for Win32 in existence.
Why the name "OpenSA"?
OpenSA is the short term for Open Server Architecture project. But what the hell does this mean? When I started the project, there was no easy to use and full-featured Apache distribution, so i started one. My intention was to Open up the Win32 world, that's why it's called Open Server Architecture or in short: OpenSA
OK, so how does OpenSA compare to other servers?
As the OpenSA web server is Apache based, it runs at least as fast as the Internet Information Server from Microsoft.
How thoroughly tested is OpenSA?
The OpenSA web server has been tested in the field use with software like Allaire ColdFusion and Allaire Spectra with professional applications. By long-term test the fitness for usage in the professional surrounding field was tested.
What are the future plans for OpenSA?
- to continue to be an "open source" no-charge-for-use HTTP server,
- to keep up with advances in HTTP protocol and web developments in general,
- to collect suggestions for fixes/improvements from its users,
- to respond to needs of large volume providers as well as occasional users.
If you are interested in our short and long term plans, take a look at our roadmap.
Whom do I contact for support?
There is support for OpenSA. We have several mailing lists for both end users and developers up and running, all being archived for you. These can be found here.

Bug reports and suggestions should be sent via the bug report page.
We use the mantis bug tracker. So you first have to create an account before you can enter bugs and feature requests. Registration is free and no one will make use of the data you entered.

Commercial support for OpenSA is available from the company that sponsors the development of OpenSA. More information's are available on their site at www.best-off.org. Currently support is available in german and english.
Is there any more information available on OpenSA?
Indeed there is. See the main OpenSA site.
Where can I get OpenSA?
You can find out how to download the source for OpenSA at the project's main web page.
May I use the OpenSA logo on my product or Web site?
You may NOT use any original artwork from the Open Server Architecture project, nor make or use modified versions of such artwork, except under the following conditions:
- You may use the 'Powered by OpenSA' graphic on a Web site that is being served by the OpenSA web server software.
- You may use the aforementioned 'Powered by OpenSA' graphic or the OpenSA project logo in product description and promotional material IF and ONLY IF such use can in no way be interpreted as anything other than an attribution. Using the OpenSA name and artwork in a manner that implies endorsement of a product or service is strictly forbidden.

B. General information

What requirements has the current release?
The OpenSA web server can be used on any hardware you wish. Either for testing purposes on a small Windows® 9x system or for high- volume commercial sites on dual-processor systems.

If you're not sure, how stable the OpenSA web server runs, we suggest to take a look ate the Real World section of the OpenSA project's site. There you'll find some sites using the OpenSA web server in commercial projects.
Why did it take so long to release the 1.0.0 final?
The OpenSA distribution has undergone many changes in the last months, therefore it took quite long to release a final version. Major rework has been done now. Therefore OpenSA 1.0.0 has been release to the public.
What is the roadmap for future versions?
OpenSA packages should now be updated quicker with the new build system that was implemented by the developers. We will hold close to the Apache release cycle to always keep you in touch with new releases.

C. Update information

How do i update to a new beta release?
Although beta versions contain stable versions of Apache and it's modules, there may be changes in the installation system that could make updates from previous OpenSA releases problematic.

In general we advise you to make backups of all your configuration files:
- Apache config files (httpd.conf, access.conf, srm.conf)
- SSL server keyfiles/certificates
- OpenSSL config files (openssl.cnf, oid.cnf)
- all files in the standard document root
After that you should remove your old installation and then install the new release. Afterwards check for changes in the config files, especially changes in module configurations may change from version to version. Usually you can copy your backup back to the Apache and OpenSSL installation folders and then fire up Apache.

If not stated otherwise in the release announcement, it is preferred to update to new beta releases in this way. That's why they are beta releases.
How do i update to a new final release?
Final releases have proven to be stable, including both the included packages and the installation system. Therefore you can overwrite old beta and final releases you may have installed.
In general the same applies as with beta versions: make backups of all your configuration files!
- Apache config files (httpd.conf, access.conf, srm.conf)
- SSL server keyfiles/certificates
- OpenSSL config files (openssl.cnf, oid.cnf)
- all files in the standard document root
The final version will update your existing configuration files where possible. Otherwise new files will be generated, which look like httpd.conf-dist-new.

D. Supporting OpenSA

Can I help in writing docs etc.?
Yes of course. Any kind of help is welcome. Since the OpenSA team currently only consists of one member and many users, we urgently need help with this issue.
Just contact the current developer Daniel S. Reichenbach <dsr@best-off.org> if you want to assist.
Can I help in development of OpenSA?
Of course, we have many places where an encouraged developer could help. Especially the ASP support and Apache 2.0 preparations will need some more developers to take an eye on it.
Just contact the current developer Daniel S. Reichenbach <dsr@best-off.org> if you want to assist.