Apache server Frequently Asked Questions

The Questions

  1. What is Apache ?
  2. Why was Apache created ?
  3. How does the Apache group relate to the NCSA 1.4 effort ?
  4. Why the name "Apache" ?
  5. How compatible is Apache with my existing NCSA 1.3 setup ?
  6. Why didn't the Apache group wait for NCSA 1.4 ?
  7. OK, so how does Apache compare to other servers ?
  8. How thoroughly tested is Apache?
  9. What extensions does Apache offer over NCSA 1.x?
  10. What NCSA 1.3 bugs are fixed in Apache ?
  11. What are the future plans for Apache ?
  12. Who do I contact for support ?
  13. Is there any more information on Apache ?
  14. Where can get Apache ?

The Answers

  1. What is Apache ?

    Apache is a server based on NCSA httpd 1.3. It has several new features (among which are highly configurable error messages, DBM-based authentication databases, and content negotiation). It also offers dramatically improved performance, and fixes many bugs in the NCSA 1.3 code.

  2. How does the Apache group relate to the NCSA 1.4 effort ?

    We are, of course, aware of NCSA's ongoing efforts towards the release of a 1.4 version of their server (as they are aware of ours; in fact, the current NCSA beta contains some code written by members of the Apache group). Once NCSA 1.4 has been released, we hope to incorporate most of its innovations (and perhaps to transition entirely to a 1.4 code base). However, these are independent efforts.

  3. Why was Apache created ?

    to address concerns of a group of www providers and part time httpd programmers, that httpd didn't behave as they wanted it to.

  4. Why the name "Apache" ?

    A cute name which stuck. Apache is "A PAtCHy server". It was based on some existing code and a series of "patch files".

  5. How compatible is Apache with my existing NCSA 1.3 setup ?

    Apache is 100% compatible with your existing NCSA 1.3 setup. Apache is a plug in replacement.

  6. Why didn't the Apache group wait for NCSA 1.4 ?

    we didn't expect the features we needed to show up in a near-term NCSA release. Furthermore, uncertainty over the future of the NCSA httpd license worried some of us. Apache is and will be a public domain server. With its collaborative development team we openly welcome new volunteers, suggestions and support.

  7. OK, so how does Apache compare to other servers ?

    For an independent assessment, see http://mistral.enst.fr/~pioch/httpd/

  8. How thoroughly tested is Apache?

    Version 0.6.2 of Apache was 'plugged in' at,

    www.hotwired.com
    IRIX.
    Hits/day 400,000+ (from 2 machines)
    www.ai.mit.edu
    SunOS.
    Hits/day 100,000+
    www.msstate.edu
    Solaris
    Hits/day 100,000+
    heavy use of CGI
    www.cm.cf.ac.uk
    SunOS.
    Hits/day 100,000+
    heavy use of CGI
    www.hyperreal.com
    BSDI.
    Hits/day 40,000+

    Also tested under HPUX

    As you can see, these machines run services which are far busier than the average httpd server, so Apache has received a considerable workout. It works for us; however, this is beta code, and again, your mileage may vary.

  9. What extensions does Apache offer over NCSA 1.x ?

    Here are just some of the new features...

    Four ways of customizing error responses

    hard-coded responses, customizable text responses, local URL redirection, external URL redirection.

    Virtual-home

    A server running on a machine with multiple IP addresses can have a different home page for each IP address

    Additional CGI variables

    n.b. non-standard at the moment. The new CGI variables help scripts and server-side-includes be more aware of their environment and origin.

    Content negotiation

    Clients can negotiate the type of information they prefer, e.g. jpeg rather than gif, German instead of the default English, dvi instead of postscript.

    As clients improve in terms of user configurability, content negotiation will become a powerful and much system to give users what they want, instead of defaulting to some low common denominator.

    XBITHACK Last-modified:

    XBITHACK can be configured to send back a Last-modified: header to enable clients and proxies to cache documents which make use of XBITHACKed server-side includes.

    Better CGI script control

    CGI scripts can send back custom HTTP response headers as well as a body after an external redirect. An example of a custom response header,

    Status 404: URL was not found
    Improved logging of redirected URLs

    If a request results in a redirect to another URL, both URLs are logged in the access_log

    Multiple DirecotryIndex filenames

    Apache will search for index.html as well as any other filenames you prefer.

  10. What NCSA 1.3 bugs are fixed in Apache ?

    1. Efficiency...no longer does initgroups() or open_locale() on every connection, no longer does single- character read() system calls *ever*.

    2. Fixed a condition that was leading to un-killable httpd processes piling up on server machines and chewing up swap space.

    3. Unlimited numbers of Aliases and Redirects are allowed.

    4. AddTypes for the CGI and SERVER_INCLUDES magic MIME types are honored in .htaccess files.

    5. Auth_user is correctly logged for password-protected documents with server-side includes.

    6. Scripts can return Content-types with embedded blanks.

    7. Security hole allowing cgi script sources to be viewed, removed.

    8. Handling of redirects from scripts improved (no more mandatory three-second pauses on imagemap hits).

    9. XBITHACK also checks X-bits of included files.

  11. What are the future plans for Apache ?

  12. Who do I contact for support ?

    You get what you pay for :-)

    There is no official support for Apache. None of the developers want to be swamped by a flood of trivial questions that can be resolved elsewhere. Bug reports and suggestions should be sent to apache-bugs@mail.apache.org Other questions should be directed to comp.infosystems.www.servers.unix, where some of the Apache team lurk, in the company of many other httpd gurus who should be able to help.

  13. Is there any more information on Apache ?

    Indeed there is. See http://www.apache.org/apache/.

  14. Where can get Apache ?

    You can find the source for Apache at http://www.apache.org/apache/dist/.

Home Index