docs/manual/misc/FAQ-A.html - httpd - Git at Google

 <!--#if expr="$FAQMASTER" -->
  <!--#set var="STANDALONE" value="" -->
  <!--#set var="INCLUDED" value="YES" -->
  <!--#if expr="$QUERY_STRING = TOC" -->
   <!--#set var="TOC" value="YES" -->
   <!--#set var="CONTENT" value="" -->
  <!--#else -->
   <!--#set var="TOC" value="" -->
   <!--#set var="CONTENT" value="YES" -->
  <!--#endif -->
 <!--#else -->
  <!--#set var="STANDALONE" value="YES" -->
  <!--#set var="INCLUDED" value="" -->
  <!--#set var="TOC" value="" -->
  <!--#set var="CONTENT" value="" -->
 <!--#endif -->
 <!--#if expr="$STANDALONE" -->
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
 <HTML>
  <HEAD>
   <TITLE>Apache Server Frequently Asked Questions</TITLE>
  </HEAD>
 <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  <BODY
   BGCOLOR="#FFFFFF"
   TEXT="#000000"
   LINK="#0000FF"
   VLINK="#000080"
   ALINK="#FF0000"
  >
   <!--#include virtual="header.html" -->
   <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
   <P>
   $Revision: 1.3 $ ($Date: 1999/12/31 23:11:17 $)
   </P>
   <P>
   The latest version of this FAQ is always available from the main
   Apache web site, at
   &lt;<A
        HREF="http://www.apache.org/docs/misc/FAQ.html"
        REL="Help"
       ><SAMP>http://www.apache.org/docs/misc/FAQ.html</SAMP></A>&gt;.
   </P>
 <!-- Notes about changes:                                           -->
 <!--  - If adding a relative link to another part of the            -->
 <!--    documentation, *do* include the ".html" portion.  There's a -->
 <!--    good chance that the user will be reading the documentation -->
 <!--    on his own system, which may not be configured for          -->
 <!--    multiviews.                                                 -->
 <!--  - When adding items, make sure they're put in the right place -->
 <!--    - verify that the numbering matches up.                     -->
 <!--  - *Don't* use <PRE></PRE> blocks - they don't appear          -->
 <!--    correctly in a reliable way when this is converted to text  -->
 <!--    with Lynx.  Use <DL><DD><CODE>xxx<BR>xx</CODE></DD></DL>    -->
 <!--    blocks inside a <P></P> instead.  This is necessary to get  -->
 <!--    the horizontal and vertical indenting right.                -->
 <!--  - Don't forget to include an HR tag after the last /P tag     -->
 <!--    but before the /LI in an item.                              -->
   <P>
   If you are reading a text-only version of this FAQ, you may find numbers
   enclosed in brackets (such as &quot;[12]&quot;).  These refer to the list of
   reference URLs to be found at the end of the document.  These references
   do not appear, and are not needed, for the hypertext version.
   </P>
   <H2>The Questions</H2>
 <OL TYPE="A">
 <!--#endif -->
 <!--#if expr="$TOC || $STANDALONE" -->
  <LI VALUE="1"><STRONG>Background</STRONG>
   <OL>
    <LI><A HREF="#what">What is Apache?</A>
    </LI>
    <LI><A HREF="#why">Why was Apache created?</A>
    </LI>
    <LI><A HREF="#relate">How does The Apache Group's work relate to
     other servers?</A>
    </LI>
    <LI><A HREF="#name">Why the name &quot;Apache&quot;?</A>
    </LI>
    <LI><A HREF="#compare">OK, so how does Apache compare to other servers?</A>
    </LI>
    <LI><A HREF="#tested">How thoroughly tested is Apache?</A>
    </LI>
    <LI><A HREF="#future">What are the future plans for Apache?</A>
    </LI>
    <LI><A HREF="#support">Whom do I contact for support?</A>
    </LI>
    <LI><A HREF="#more">Is there any more information on Apache?</A>
    </LI>
    <LI><A HREF="#where">Where can I get Apache?</A>
    </LI>
   </OL>
  </LI>
 <!--#endif -->
 <!--#if expr="$STANDALONE" -->
 </OL>

 <HR>

   <H2>The Answers</H2>
 <!--#endif -->
 <!--#if expr="! $TOC" -->
   <H3>A. Background</H3>
 <OL>
  <LI><A NAME="what">
       <STRONG>What is Apache?</STRONG>
      </A>
   <P>
   Apache was originally based on code and ideas found in the most
   popular HTTP server of the time.. NCSA httpd 1.3 (early 1995). It has
   since evolved into a far superior system which can rival (and probably
   surpass) almost any other UNIX based HTTP server in terms of functionality,
   efficiency and speed.
   </P>
   <P>
   Since it began, it has been completely rewritten, and includes many new
   features. Apache is, as of January 1997, the most popular WWW server on
   the Internet, according to the
   <A HREF="http://www.netcraft.com/Survey/">Netcraft Survey</A>.
   </P>
   <HR>
  </LI>

  <LI><A NAME="why">
       <STRONG>Why was Apache created?</STRONG>
      </A>
   <P>
   To address the concerns of a group of WWW providers and part-time httpd
   programmers that httpd didn't behave as they wanted it to behave.
   Apache is an entirely volunteer effort, completely funded by its
   members, not by commercial sales.
   </P>
   <HR>
  </LI>

  <LI><A NAME="relate">
       <STRONG>How does The Apache Group's work relate to other
       server efforts, such as NCSA's?</STRONG>
      </A>
   <P>
   We, of course, owe a great debt to NCSA and their programmers for
   making the server Apache was based on. We now, however, have our own
   server, and our project is mostly our own. The Apache Project is an
   entirely independent venture.
   </P>
   <HR>
  </LI>

  <LI><A NAME="name">
       <STRONG>Why the name &quot;Apache&quot;?</STRONG>
       </A>
   <P>
   A cute name which stuck. Apache is &quot;<STRONG>A
   PA</STRONG>t<STRONG>CH</STRONG>y server&quot;.  It was
   based on some existing code and a series of &quot;patch files&quot;.
   </P>

   <P>
   For many developers it is also a reverant connotation to the Native
   American Indian tribe of Apache, <A
   HREF="http://www.indians.org/welker/apache.htm">well-known for their
   superior skills in warfare strategy and inexhaustible endurance</A>.
   Online information about the Apache Nation is tough to locate; we
   suggest searching
   <A HREF="http://www.google.com/search?q=Apache+Nation">Google</A>,
   <A HREF="http://www.northernlight.com/nlquery.fcg?qr=Apache+Nation">Northernlight</A>,
   <A HREF="http://infoseek.go.com/Titles?qt=Apache+Nation">Infoseek</A>, or
   <A HREF="http://www.alltheweb.com/cgi-bin/asearch?query=Apache+Nation">AllTheWeb</A>.
   </P>
   <P>
   In addition, <A
   HREF="http://www.indian.org/">http://www.indian.org/</A> and <A
   HREF="http://www.nativeweb.com/">http://www.nativeweb.com/</A> are
   two excellent resources for Native American information.
   </P>
   <HR>
  </LI>

  <LI><A NAME="compare">
       <STRONG>OK, so how does Apache compare to other servers?</STRONG>
      </A>
   <P>
   For an independent assessment, see
   <A HREF="http://webcompare.internet.com/chart.html">Web Compare</A>'s
   comparison chart.
   </P>
   <P>
   Apache has been shown to be substantially faster than many other
   free servers. Although certain commercial servers have claimed to
   surpass Apache's speed (it has not been demonstrated that any of these
   &quot;benchmarks&quot; are a good way of measuring WWW server speed at any
   rate), we feel that it is better to have a mostly-fast free server
   than an extremely-fast server that costs thousands of dollars. Apache
   is run on sites that get millions of hits per day, and they have
   experienced no performance difficulties.
   </P>
   <HR>
  </LI>

  <LI><A NAME="tested">
       <STRONG>How thoroughly tested is Apache?</STRONG>
      </A>
   <P>
   Apache is run on over 3 million Internet servers (as of June 1999). It has
   been tested thoroughly by both developers and users. The Apache Group
   maintains rigorous standards before releasing new versions of their
   server, and our server runs without a hitch on over one half of all
   WWW servers available on the Internet.  When bugs do show up, we
   release patches and new versions as soon as they are available.
   </P>
   <P>
   The Apache project's web site includes a page with a partial list of
   <A HREF="http://www.apache.org/info/apache_users.html">sites running
   Apache</A>.
   </P>
   <HR>
  </LI>

  <LI><A NAME="future">
       <STRONG>What are the future plans for Apache?</STRONG>
      </A>
   <P>
   <UL>
    <LI>to continue to be an "open source" no-charge-for-use HTTP server,
    </LI>
    <LI>to keep up with advances in HTTP protocol and web developments in
     general,
    </LI>
    <LI>to collect suggestions for fixes/improvements from its users,
    </LI>
    <LI>to respond to needs of large volume providers as well as
     occasional users.
    </LI>
   </UL>
   <P></P>
   <HR>
  </LI>

  <LI><A NAME="support">
       <STRONG>Whom do I contact for support?</STRONG>
      </A>
   <P>
   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 <EM>via</EM>
   <A HREF="http://www.apache.org/bug_report.html">the bug report page</A>.
   Other questions should be directed to the
   <A HREF="news:comp.infosystems.www.servers.unix"
   >comp.infosystems.www.servers.unix</A> or <A HREF=
   "news:comp.infosystems.www.servers.ms-windows"
   >comp.infosystems.www.servers.ms-windows</A>
   newsgroup (as appropriate for the platform you use), where some of the
   Apache team lurk, in the company of many other httpd gurus who
   should be able to help.
   </P>
   <P>
   Commercial support for Apache is, however, available from a number
   of third parties.
   </P>
   <HR>
  </LI>

  <LI><A NAME="more">
       <STRONG>Is there any more information available on
       Apache?</STRONG>
      </A>
   <P>
   Indeed there is.  See the main
   <A HREF="http://www.apache.org/">Apache web site</A>.
   There is also a regular electronic publication called
   <A HREF="http://www.apacheweek.com/" REL="Help"><CITE>Apache Week</CITE></A>
   available.  Links to relevant <CITE>Apache Week</CITE> articles are
   included below where appropriate. There are also some
   <A HREF="http://www.apache.org/info/apache_books.html"
   >Apache-specific books</A> available.
   </P>
   <HR>
  </LI>

  <LI><A NAME="where">
       <STRONG>Where can I get Apache?</STRONG>
      </A>
   <P>
   You can find out how to download the source for Apache at the
   project's
   <A HREF="http://www.apache.org/">main web page</A>.
   </P>
   <HR>
  </LI>
 </OL>
 <!--#endif -->
 <!--#if expr="$STANDALONE" -->
   <!-- Don't forget to add HR tags at the end of each list item.. -->

 <!--#include virtual="footer.html" -->
 </BODY>
 </HTML>
 <!--#endif -->
	<!--#if expr="$FAQMASTER" -->
	<!--#set var="STANDALONE" value="" -->
	<!--#set var="INCLUDED" value="YES" -->
	<!--#if expr="$QUERY_STRING = TOC" -->
	<!--#set var="TOC" value="YES" -->
	<!--#set var="CONTENT" value="" -->
	<!--#else -->
	<!--#set var="TOC" value="" -->
	<!--#set var="CONTENT" value="YES" -->
	<!--#endif -->
	<!--#else -->
	<!--#set var="STANDALONE" value="YES" -->
	<!--#set var="INCLUDED" value="" -->
	<!--#set var="TOC" value="" -->
	<!--#set var="CONTENT" value="" -->
	<!--#endif -->
	<!--#if expr="$STANDALONE" -->
	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
	<HTML>
	<HEAD>
	<TITLE>Apache Server Frequently Asked Questions</TITLE>
	</HEAD>
	<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
	<BODY
	BGCOLOR="#FFFFFF"
	TEXT="#000000"
	LINK="#0000FF"
	VLINK="#000080"
	ALINK="#FF0000"
	>
	<!--#include virtual="header.html" -->
	<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
	<P>
	$Revision: 1.3 $ ($Date: 1999/12/31 23:11:17 $)
	</P>
	<P>
	The latest version of this FAQ is always available from the main
	Apache web site, at
	<<A
	HREF="http://www.apache.org/docs/misc/FAQ.html"
	REL="Help"
	><SAMP>http://www.apache.org/docs/misc/FAQ.html</SAMP></A>>.
	</P>
	<!-- Notes about changes: -->
	<!-- - If adding a relative link to another part of the -->
	<!-- documentation, do include the ".html" portion. There's a -->
	<!-- good chance that the user will be reading the documentation -->
	<!-- on his own system, which may not be configured for -->
	<!-- multiviews. -->
	<!-- - When adding items, make sure they're put in the right place -->
	<!-- - verify that the numbering matches up. -->
	<!-- - Don't use <PRE></PRE> blocks - they don't appear -->
	<!-- correctly in a reliable way when this is converted to text -->
	<!-- with Lynx. Use <DL><DD><CODE>xxx<BR>xx</CODE></DD></DL> -->
	<!-- blocks inside a <P></P> instead. This is necessary to get -->
	<!-- the horizontal and vertical indenting right. -->
	<!-- - Don't forget to include an HR tag after the last /P tag -->
	<!-- but before the /LI in an item. -->
	<P>
	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 URLs to be found at the end of the document. These references
	do not appear, and are not needed, for the hypertext version.
	</P>
	<H2>The Questions</H2>
	<OL TYPE="A">
	<!--#endif -->
	<!--#if expr="$TOC \|\| $STANDALONE" -->
	<LI VALUE="1"><STRONG>Background</STRONG>
	<OL>
	<LI><A HREF="#what">What is Apache?</A>
	</LI>
	<LI><A HREF="#why">Why was Apache created?</A>
	</LI>
	<LI><A HREF="#relate">How does The Apache Group's work relate to
	other servers?</A>
	</LI>
	<LI><A HREF="#name">Why the name "Apache"?</A>
	</LI>
	<LI><A HREF="#compare">OK, so how does Apache compare to other servers?</A>
	</LI>
	<LI><A HREF="#tested">How thoroughly tested is Apache?</A>
	</LI>
	<LI><A HREF="#future">What are the future plans for Apache?</A>
	</LI>
	<LI><A HREF="#support">Whom do I contact for support?</A>
	</LI>
	<LI><A HREF="#more">Is there any more information on Apache?</A>
	</LI>
	<LI><A HREF="#where">Where can I get Apache?</A>
	</LI>
	</OL>
	</LI>
	<!--#endif -->
	<!--#if expr="$STANDALONE" -->
	</OL>

	<HR>

	<H2>The Answers</H2>
	<!--#endif -->
	<!--#if expr="! $TOC" -->
	<H3>A. Background</H3>
	<OL>
	<LI><A NAME="what">
	<STRONG>What is Apache?</STRONG>
	</A>
	<P>
	Apache was originally based on code and ideas found in the most
	popular HTTP server of the time.. NCSA httpd 1.3 (early 1995). It has
	since evolved into a far superior system which can rival (and probably
	surpass) almost any other UNIX based HTTP server in terms of functionality,
	efficiency and speed.
	</P>
	<P>
	Since it began, it has been completely rewritten, and includes many new
	features. Apache is, as of January 1997, the most popular WWW server on
	the Internet, according to the
	<A HREF="http://www.netcraft.com/Survey/">Netcraft Survey</A>.
	</P>
	<HR>
	</LI>

	<LI><A NAME="why">
	<STRONG>Why was Apache created?</STRONG>
	</A>
	<P>
	To address the concerns of a group of WWW providers and part-time httpd
	programmers that httpd didn't behave as they wanted it to behave.
	Apache is an entirely volunteer effort, completely funded by its
	members, not by commercial sales.
	</P>
	<HR>
	</LI>

	<LI><A NAME="relate">
	<STRONG>How does The Apache Group's work relate to other
	server efforts, such as NCSA's?</STRONG>
	</A>
	<P>
	We, of course, owe a great debt to NCSA and their programmers for
	making the server Apache was based on. We now, however, have our own
	server, and our project is mostly our own. The Apache Project is an
	entirely independent venture.
	</P>
	<HR>
	</LI>

	<LI><A NAME="name">
	<STRONG>Why the name "Apache"?</STRONG>
	</A>
	<P>
	A cute name which stuck. Apache is "<STRONG>A
	PA</STRONG>t<STRONG>CH</STRONG>y server". It was
	based on some existing code and a series of "patch files".
	</P>

	<P>
	For many developers it is also a reverant connotation to the Native
	American Indian tribe of Apache, <A
	HREF="http://www.indians.org/welker/apache.htm">well-known for their
	superior skills in warfare strategy and inexhaustible endurance</A>.
	Online information about the Apache Nation is tough to locate; we
	suggest searching
	<A HREF="http://www.google.com/search?q=Apache+Nation">Google</A>,
	<A HREF="http://www.northernlight.com/nlquery.fcg?qr=Apache+Nation">Northernlight</A>,
	<A HREF="http://infoseek.go.com/Titles?qt=Apache+Nation">Infoseek</A>, or
	<A HREF="http://www.alltheweb.com/cgi-bin/asearch?query=Apache+Nation">AllTheWeb</A>.
	</P>
	<P>
	In addition, <A
	HREF="http://www.indian.org/">http://www.indian.org/</A> and <A
	HREF="http://www.nativeweb.com/">http://www.nativeweb.com/</A> are
	two excellent resources for Native American information.
	</P>
	<HR>
	</LI>

	<LI><A NAME="compare">
	<STRONG>OK, so how does Apache compare to other servers?</STRONG>
	</A>
	<P>
	For an independent assessment, see
	<A HREF="http://webcompare.internet.com/chart.html">Web Compare</A>'s
	comparison chart.
	</P>
	<P>
	Apache has been shown to be substantially faster than many other
	free servers. Although certain commercial servers have claimed to
	surpass Apache's speed (it has not been demonstrated that any of these
	"benchmarks" are a good way of measuring WWW server speed at any
	rate), we feel that it is better to have a mostly-fast free server
	than an extremely-fast server that costs thousands of dollars. Apache
	is run on sites that get millions of hits per day, and they have
	experienced no performance difficulties.
	</P>
	<HR>
	</LI>

	<LI><A NAME="tested">
	<STRONG>How thoroughly tested is Apache?</STRONG>
	</A>
	<P>
	Apache is run on over 3 million Internet servers (as of June 1999). It has
	been tested thoroughly by both developers and users. The Apache Group
	maintains rigorous standards before releasing new versions of their
	server, and our server runs without a hitch on over one half of all
	WWW servers available on the Internet. When bugs do show up, we
	release patches and new versions as soon as they are available.
	</P>
	<P>
	The Apache project's web site includes a page with a partial list of
	<A HREF="http://www.apache.org/info/apache_users.html">sites running
	Apache</A>.
	</P>
	<HR>
	</LI>

	<LI><A NAME="future">
	<STRONG>What are the future plans for Apache?</STRONG>
	</A>
	<P>
	<UL>
	<LI>to continue to be an "open source" no-charge-for-use HTTP server,
	</LI>
	<LI>to keep up with advances in HTTP protocol and web developments in
	general,
	</LI>
	<LI>to collect suggestions for fixes/improvements from its users,
	</LI>
	<LI>to respond to needs of large volume providers as well as
	occasional users.
	</LI>
	</UL>
	<P></P>
	<HR>
	</LI>

	<LI><A NAME="support">
	<STRONG>Whom do I contact for support?</STRONG>
	</A>
	<P>
	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 <EM>via</EM>
	<A HREF="http://www.apache.org/bug_report.html">the bug report page</A>.
	Other questions should be directed to the
	<A HREF="news:comp.infosystems.www.servers.unix"
	>comp.infosystems.www.servers.unix</A> or <A HREF=
	"news:comp.infosystems.www.servers.ms-windows"
	>comp.infosystems.www.servers.ms-windows</A>
	newsgroup (as appropriate for the platform you use), where some of the
	Apache team lurk, in the company of many other httpd gurus who
	should be able to help.
	</P>
	<P>
	Commercial support for Apache is, however, available from a number
	of third parties.
	</P>
	<HR>
	</LI>

	<LI><A NAME="more">
	<STRONG>Is there any more information available on
	Apache?</STRONG>
	</A>
	<P>
	Indeed there is. See the main
	<A HREF="http://www.apache.org/">Apache web site</A>.
	There is also a regular electronic publication called
	<A HREF="http://www.apacheweek.com/" REL="Help"><CITE>Apache Week</CITE></A>
	available. Links to relevant <CITE>Apache Week</CITE> articles are
	included below where appropriate. There are also some
	<A HREF="http://www.apache.org/info/apache_books.html"
	>Apache-specific books</A> available.
	</P>
	<HR>
	</LI>

	<LI><A NAME="where">
	<STRONG>Where can I get Apache?</STRONG>
	</A>
	<P>
	You can find out how to download the source for Apache at the
	project's
	<A HREF="http://www.apache.org/">main web page</A>.
	</P>
	<HR>
	</LI>
	</OL>
	<!--#endif -->
	<!--#if expr="$STANDALONE" -->
	<!-- Don't forget to add HR tags at the end of each list item.. -->

	<!--#include virtual="footer.html" -->
	</BODY>
	</HTML>
	<!--#endif -->