FAQ.html | searchcode

/mod_perl/apache_1.3.23/htdocs/manual/misc/FAQ.html

Large files files are truncated, but you can click here to view the full file

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta name="generator" content="HTML Tidy, see www.w3.org" />

    <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">
        <div align="CENTER">
      <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> 

      <h3>Apache HTTP Server Version 1.3</h3>
    </div>


    <h1 align="CENTER">Apache Server Frequently Asked
    Questions</h1>

    <p>$Revision: 1.149 $ ($Date: 2001/10/08 01:26:54 $)</p>

    <p>The latest version of this FAQ is always available from the
    main Apache web site, at &lt;<a
    href="http://httpd.apache.org/docs/misc/FAQ.html"
    rel="Help"><samp>http://httpd.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 "[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>
    <!-- Stuff to Add:                                                  -->
    <!-- - can't bind to port 80                                        -->
    <!--   - permission denied                                          -->
    <!--   - address already in use                                     -->
    <!-- - mod_auth & passwd lines "user:pw:.*" - ++1st colon onward is -->
    <!--   treated as pw, not just ++1st to \-\-2nd.                    -->
    <!-- - SSL:                                                         -->
    <!--   - Can I use Apache-SSL for free in Canada?                   -->
    <!--   - Why can't I use Apache-SSL in the U.S.?                    -->
    <!-- - How can I found out how many visitors my site gets?          -->
    <!-- - How do I add a counter?                                      -->
    <!-- - How do I configure Apache as a proxy?                        -->
    <!-- - What browsers support HTTP/1.1?                              -->
    <!-- - What's the point of vhosts-by-name is there aren't any       -->
    <!--   HTTP/1.1 browsers?                                           -->
    <!-- - Is there an Apache for W95/WNT?                              -->
    <!-- - Why does Apache die when a vhost can't be DNS-resolved?      -->
    <!-- - Why do I get "send lost connection" messages in my error     -->
    <!--   log?                                                         -->
    <!--   - specifically consider .pdf files which seem to cause this  -->
    <!--     a lot when accessed via the plugin ... and also mention    -->
    <!--     how range-requests can cause bytes served < file size      -->
    <!-- - Why do directory indexes appear as garbage?  (A: -lucb)      -->
    <!-- - How do I add a footer to all pages offered by my server?     -->
    <!-- - Fix midi question; a bigger problem than midi vs. x-midi is  -->
    <!--   the simple fact that older versions of Apache (and new ones  -->
    <!--   that have been upgraded without upgrading the mime.types     -->
    <!--   file) don't have the type listed at all.                     -->
    <!-- - RewriteRule /~fraggle/* /cgi-bin/fraggle.pl does not work    -->
    <!-- - how do I disable authentication for a subdirectory?          -->
    <!--   (A: you can't but "Satisfy any; Allow from all" can be close -->
    <!-- - '400 malformed request' on Win32 might mean stale proxy; see -->
    <!--   PR #2300.                                                    -->
    <!-- - how do I tell what version of Apache I am running?           -->

    <ol type="A">
      








      

      <li value="1">
        <strong>Background</strong> 

        <ol>
          <li><a href="#what">What is Apache?</a></li>

          <li><a href="#why">How and why was Apache
          created?</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>

          <li><a href="#logo">May I use the Apache logo on my
          product or Web site?</a></li>
        </ol>
      </li>
      
      
    
    
  </body>
</html>


      








      

      <li value="2">
        <strong>General Technical Questions</strong> 

        <ol>
          <li><a href="#what2do">"Why can't I ...? Why won't ...
          work?" What to do in case of problems</a></li>

          <li><a href="#compatible">How compatible is Apache with
          my existing NCSA 1.3 setup?</a></li>

          <li><a href="#year2000">Is Apache Year 2000
          compliant?</a></li>

          <li><a href="#submit_patch">How do I submit a patch to
          the Apache Group?</a></li>

          <li><a href="#domination">Why has Apache stolen my
          favourite site's Internet address?</a></li>

          <li><a href="#apspam">Why am I getting spam mail from the
          Apache site?</a></li>

          <li><a href="#redist">May I include the Apache software
          on a CD or other package I'm distributing?</a></li>

          <li><a href="#zoom">What's the best hardware/operating
          system/... How do I get the most out of my Apache Web
          server?</a></li>

          <li><a href="#regex">What are "regular
          expressions"?</a></li>

          <li><a href="#binaries">Why isn't there a binary for my
          platform?</a></li>
        </ol>
      </li>
      
      
    
    
  </body>
</html>


      








      

      <li value="3">
        <strong>Building Apache</strong> 

        <ol>
          <li><a href="#bind8.1">Why do I get an error about an
          undefined reference to "<samp>__inet_ntoa</samp>" or
          other <samp>__inet_*</samp> symbols?</a></li>

          <li><a href="#cantbuild">Why won't Apache compile with my
          system's <samp>cc</samp>?</a></li>

          <li><a href="#linuxiovec">Why do I get complaints about
          redefinition of "<code>struct iovec</code>" when
          compiling under Linux?</a></li>

          <li><a href="#broken-gcc">I'm using gcc and I get some
          compilation errors, what is wrong?</a></li>

          <li><a href="#glibc-crypt">I'm using RedHat Linux 5.0, or
          some other <samp>glibc</samp>-based Linux system, and I
          get errors with the <code>crypt</code> function when I
          attempt to build Apache 1.2.</a></li>
        </ol>
      </li>
      
      
    
    
  </body>
</html>


      








      

      <li value="4">
        <strong>Error Log Messages and Problems Starting
        Apache</strong> 

        <ol>
          <li><a href="#setgid">Why do I get "<samp>setgid: Invalid
          argument</samp>" at startup?</a></li>

          <li><a href="#nodelay">Why am I getting "<samp>httpd:
          could not set socket option TCP_NODELAY</samp>" in my
          error log?</a></li>

          <li><a href="#peerreset">Why am I getting
          "<samp>connection reset by peer</samp>" in my error
          log?</a></li>

          <li><a href="#wheres-the-dump">The errorlog says Apache
          dumped core, but where's the dump file?</a></li>

          <li><a href="#linux-shmget">When I run it under Linux I
          get "shmget: function not found", what should I
          do?</a></li>

          <li><a href="#nfslocking">Server hangs, or fails to
          start, and/or error log fills with "<samp>fcntl:
          F_SETLKW: No record locks available</samp>" or similar
          messages</a></li>

          <li><a href="#aixccbug">Why am I getting "<samp>Expected
          &lt;/Directory&gt; but saw &lt;/Directory&gt;</samp>"
          when I try to start Apache?</a></li>

          <li><a href="#redhat">I'm using RedHat Linux and I have
          problems with httpd dying randomly or not restarting
          properly</a></li>

          <li><a href="#stopping">I upgraded from an Apache version
          earlier than 1.2.0 and suddenly I have problems with
          Apache dying randomly or not restarting properly</a></li>

          <li><a href="#setservername">When I try to start Apache
          from a DOS window, I get a message like "<samp>Cannot
          determine host name. Use ServerName directive to set it
          manually.</samp>" What does this mean?</a></li>

          <li><a href="#ws2_32dll">When I try to start Apache for
          Windows, I get a message like "<samp>Unable To Locate
          WS2_32.DLL...</samp>". What should I do?</a></li>

          <li><a href="#WSADuplicateSocket">Apache for Windows does
          not start. Error log contains this message "<samp>[crit]
          (10045) The attempted operation is not supported for the
          type of object referenced: Parent: WSADuplicateSocket
          failed for socket ###</samp>". What does this
          mean?</a></li>

          <li><a href="#err1067">When I try to start Apache on
          Windows, I get a message like "<code>System error 1067
          has occurred. The process terminated
          unexpectedly.</code>" What does this mean?</a></li>

          <li><a href="#suseFDN">On a SuSE Linux system, I try and 
          configure access control using basic authentication.
	  Although I follow the example exactly, authentication
	  fails, and an error message "<code>admin: not a valid
	  FDN: ....</code>" is logged.</a></li>

          <li><a href="#codered">Why do I have weird entries in my
          logs asking for <code>default.ida</code> and
          <code>cmd.exe</code>?</a></li>
        </ol>
      </li>
      
      
    
    
  </body>
</html>


      








      

      <li value="5">
        <strong>Configuration Questions</strong> 

        <ol>
          <li><a href="#fdlim">Why can't I run more than
          &lt;<em>n</em>&gt; virtual hosts?</a></li>

          <li><a href="#freebsd-setsize">Can I increase
          <samp>FD_SETSIZE</samp> on FreeBSD?</a></li>

          <li><a href="#errordoc401">Why doesn't my
          <code>ErrorDocument 401</code> work?</a></li>

          <li><a href="#cookies1">Why does Apache send a cookie on
          every response?</a></li>

          <li><a href="#cookies2">Why don't my cookies work, I even
          compiled in <samp>mod_cookies</samp>?</a></li>

          <li><a href="#jdk1-and-http1.1">Why do my Java app[let]s
          give me plain text when I request an URL from an Apache
          server?</a></li>

          <li><a href="#midi">How do I get Apache to send a MIDI
          file so the browser can play it?</a></li>

          <li><a href="#addlog">How do I add browsers and referrers
          to my logs?</a></li>

          <li><a href="#set-servername">Why does accessing
          directories only work when I include the trailing "/"
          (<em>e.g.</em>,&nbsp;<samp>http://foo.domain.com/~user/</samp>)
          but not when I omit it
          (<em>e.g.</em>,&nbsp;<samp>http://foo.domain.com/~user</samp>)?</a></li>

          <li><a href="#no-info-directives">Why doesn't mod_info
          list any directives?</a></li>

          <li><a href="#namevhost">I upgraded to Apache 1.3 and now
          my virtual hosts don't work!</a></li>

          <li><a href="#redhat-htm">I'm using RedHat Linux and my
          .htm files are showing up as HTML source rather than
          being formatted!</a></li>

          <li><a href="#htaccess-work">My <code>.htaccess</code>
          files are being ignored.</a></li>

          <li><a href="#forbidden">Why do I get a
          "<samp>Forbidden</samp>" message whenever I try to access
          a particular directory?</a></li>

          <li><a href="#malfiles">Why do I get a
          "<samp>Forbidden/You don't have permission to access / on
          this server</samp>" message whenever I try to access my
          server?</a></li>

          <li><a href="#ie-ignores-mime">Why do my files appear
          correctly in Internet Explorer, but show up as source or
          trigger a save window with Netscape?</a></li>

	  <li><a href="#canonical-hostnames">My site is accessible
          under many different hostnames; how do I redirect clients
          so that they see only a single name?</a></li>

          <li><a href="#firewall">Why can I access my website from the
          server or from my local network, but I can't access it from
          elsewhere on the Internet?</a></li>

        </ol>
      </li>
      
      
    
    
  </body>
</html>


      








      

      <li value="6">
        <strong>Dynamic Content (CGI and SSI)</strong> 

        <ol>
          <li><a href="#CGIoutsideScriptAlias">How do I enable CGI
          execution in directories other than the
          ScriptAlias?</a></li>

          <li><a href="#premature-script-headers">What does it mean
          when my CGIs fail with "<samp>Premature end of script
          headers</samp>"?</a></li>

          <li><a href="#POSTnotallowed">Why do I keep getting
          "Method Not Allowed" for form POST requests?</a></li>

          <li><a href="#nph-scripts">How can I get my script's
          output without Apache buffering it? Why doesn't my server
          push work?</a></li>

          <li><a href="#cgi-spec">Where can I find the "CGI
          specification"?</a></li>

          <li><a href="#fastcgi">Why isn't FastCGI included with
          Apache any more?</a></li>

          <li><a href="#ssi-part-i">How do I enable SSI (parsed
          HTML)?</a></li>

          <li><a href="#ssi-part-ii">Why don't my parsed files get
          cached?</a></li>

          <li><a href="#ssi-part-iii">How can I have my script
          output parsed?</a></li>

          <li><a href="#ssi-part-iv">SSIs don't work for
          VirtualHosts and/or user home directories</a></li>

          <li><a href="#errordocssi">How can I use
          <code>ErrorDocument</code> and SSI to simplify customized
          error messages?</a></li>

          <li><a href="#remote-user-var">Why is the environment
          variable <samp>REMOTE_USER</samp> not set?</a></li>

          <li><a href="#user-cgi">How do I allow each of my user
          directories to have a cgi-bin directory?</a></li>
        </ol>
      </li>
      
      
    
    
  </body>
</html>


      








      

      <li value="7">
        <strong>Authentication and Access Restrictions</strong> 

        <ol>
          <li><a href="#dnsauth">Why isn't restricting access by
          host or domain name working correctly?</a></li>

          <li><a href="#user-authentication">How do I set up Apache
          to require a username and password to access certain
          documents?</a></li>

          <li><a href="#remote-auth-only">How do I set up Apache to
          allow access to certain documents only if a site is
          either a local site <em>or</em> the user supplies a
          password and username?</a></li>

          <li><a href="#authauthoritative">Why does my
          authentication give me a server error?</a></li>

          <li><a href="#auth-on-same-machine">Do I have to keep the
          (mSQL) authentication information on the same
          machine?</a></li>

          <li><a href="#msql-slow">Why is my mSQL authentication
          terribly slow?</a></li>

          <li><a href="#passwdauth">Can I use my
          <samp>/etc/passwd</samp> file for Web page
          authentication?</a></li>

          <li><a href="#prompted-twice">Why does Apache ask for my
          password twice before serving a file?</a></li>
        </ol>
      </li>
      
      
    
    
  </body>
</html>


      








      

      <li value="8">
        <strong>URL Rewriting</strong> 

        <ol>
          <li><a href="#rewrite-more-config">Where can I find
          mod_rewrite rulesets which already solve particular
          URL-related problems?</a></li>

          <li><a href="#rewrite-article">Where can I find any
          published information about URL-manipulations and
          mod_rewrite?</a></li>

          <li><a href="#rewrite-complexity">Why is mod_rewrite so
          difficult to learn and seems so complicated?</a></li>

          <li><a href="#rewrite-dontwork">What can I do if my
          RewriteRules don't work as expected?</a></li>

          <li><a href="#rewrite-prefixdocroot">Why don't some of my
          URLs get prefixed with DocumentRoot when using
          mod_rewrite?</a></li>

          <li><a href="#rewrite-nocase">How can I make all my URLs
          case-insensitive with mod_rewrite?</a></li>

          <li><a href="#rewrite-virthost">Why are RewriteRules in
          my VirtualHost parts ignored?</a></li>

          <li><a href="#rewrite-envwhitespace">How can I use
          strings with whitespaces in RewriteRule's ENV
          flag?</a></li>
        </ol>
      </li>
      
      
    
    
  </body>
</html>


      








      

      <li value="9">
        <strong>Features</strong> 

        <ol>
          <li><a href="#proxy">Does or will Apache act as a Proxy
          server?</a></li>

          <li><a href="#multiviews">What are "multiviews"?</a></li>

          <li><a href="#putsupport">Why can't I publish to my
          Apache server using PUT on Netscape Gold and other
          programs?</a></li>

          <li><a href="#SSL-i">Why doesn't Apache include
          SSL?</a></li>

          <li><a href="#footer">How can I attach a footer to my
          documents without using SSI?</a></li>

          <li><a href="#search">Does Apache include a search
          engine?</a></li>

          <li><a href="#rotate">How can I rotate my log
          files?</a></li>

          <li><a href="#conditional-logging">How do I keep certain
          requests from appearing in my logs?</a></li>

          <li><a href="#dbinteg">Does Apache include any sort of
          database integration?</a></li>

          <li><a href="#asp">Can I use Active Server Pages (ASP)
          with Apache?</a></li>

          <li><a href="#java">Does Apache come with Java
          support?</a></li>
        </ol>
      </li>
      
      
    
    
  </body>
</html>


    </ol>
    <hr />

    <h2>The Answers</h2>
    








      
      
    

    <h3>A. Background</h3>

    <ol>
      <li>
        <a id="what" name="what"><strong>What is
        Apache?</strong></a> 

        <p>The Apache httpd server</p>

        <ul>
          <li>is a powerful, flexible, HTTP/1.1 compliant web
          server</li>

          <li>implements the latest protocols, including HTTP/1.1
          (RFC2616)</li>

          <li>is highly configurable and extensible with
          third-party modules</li>

          <li>can be customised by writing 'modules' using the
          Apache module API</li>

          <li>provides full source code and comes with an
          unrestrictive license</li>

          <li>runs on Windows NT/9x, Netware 5.x, OS/2, and most
          versions of Unix, as well as several other operating
          systems</li>

          <li>is actively being developed</li>

          <li>encourages user feedback through new ideas, bug
          reports and patches</li>

          <li>
            implements many frequently requested features,
            including:<br />
            <br />
             

            <dl>
              <dt>DBM databases for authentication</dt>

              <dd>allows you to easily set up password-protected
              pages with enormous numbers of authorized users,
              without bogging down the server.</dd>

              <dt>Customized responses to errors and problems</dt>

              <dd>Allows you to set up files, or even CGI scripts,
              which are returned by the server in response to
              errors and problems, e.g. setup a script to intercept
              <strong>500 Server Error</strong>s and perform
              on-the-fly diagnostics for both users and
              yourself.</dd>

              <dt>Multiple DirectoryIndex directives</dt>

              <dd>Allows you to say <code>DirectoryIndex index.html
              index.cgi</code>, which instructs the server to
              either send back <code>index.html</code> or run
              <code>index.cgi</code> when a directory URL is
              requested, whichever it finds in the directory.</dd>

              <dt>Unlimited flexible URL rewriting and
              aliasing</dt>

              <dd>Apache has no fixed limit on the numbers of
              Aliases and Redirects which may be declared in the
              config files. In addition, a powerful rewriting
              engine can be used to solve most URL manipulation
              problems.</dd>

              <dt>Content negotiation</dt>

              <dd>i.e. the ability to automatically serve clients
              of varying sophistication and HTML level compliance,
              with documents which offer the best representation of
              information that the client is capable of
              accepting.</dd>

              <dt>Virtual Hosts</dt>

              <dd>A much requested feature, sometimes known as
              multi-homed servers. This allows the server to
              distinguish between requests made to different IP
              addresses or names (mapped to the same machine).
              Apache also offers dynamically configurable
              mass-virtual hosting.</dd>

              <dt>Configurable Reliable Piped Logs</dt>

              <dd>You can configure Apache to generate logs in the
              format that you want. In addition, on most Unix
              architectures, Apache can send log files to a pipe,
              allowing for log rotation, hit filtering, real-time
              splitting of multiple vhosts into separate logs, and
              asynchronous DNS resolving on the fly.</dd>
            </dl>
          </li>
        </ul>
        <hr />
      </li>

      <li>
        <a id="why" name="why"><strong>How and why was Apache
        created?</strong></a> 

        <p>The <a
        href="http://httpd.apache.org/ABOUT_APACHE.html">About
        Apache</a> document explains how the Apache project evolved
        from its beginnings as an outgrowth of the NCSA httpd
        project to its current status as one of the fastest, most
        efficient, and most functional web servers in
        existence.</p>
        <hr />
      </li>

      <li>
        <a id="name" 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 reverent 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>. For more information on the
        Apache Nation, 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>, or <a
        href="http://www.alltheweb.com/cgi-bin/asearch?query=Apache+Nation">
        AllTheWeb</a>.</p>
        <hr />
      </li>

      <li>
        <a id="compare" 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/">Web
        Compare</a>.</p>

        <p>Apache has been shown to be substantially faster, more
        stable, and more feature-full than many other web 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 id="tested" name="tested"><strong>How thoroughly tested
        is Apache?</strong></a> 

        <p>Apache is run on over 6 million Internet servers (as of
        February 2000). 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>
        <hr />
      </li>

      <li>
        <a id="future" name="future"><strong>What are the future
        plans for Apache?</strong></a> 

        <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>
        <hr />
      </li>

      <li>
        <a id="support" 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://httpd.apache.org/bug_report.html">the bug
        report page</a>. Other questions should be directed to the
        <a href="http://httpd.apache.org/userslist.html">Apache HTTP
        Server Users List</a> or 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 id="more" name="more"><strong>Is there any more
        information available on Apache?</strong></a> 

        <p>Indeed there is. See the main <a
        href="http://httpd.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://httpd.apache.org/info/apache_books.html">Apache-specific
        books</a> available.</p>
        <hr />
      </li>

      <li>
        <a id="where" 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://httpd.apache.org/">main
        web page</a>.</p>
        <hr />
      </li>

      <li>
        <a id="logo" name="logo"><b>May I use the Apache logo on my
        product or Web site?</b></a> 

        <p>You may <b>NOT</b> use any original artwork from the
        Apache Software Foundation, nor make or use modified
        versions of such artwork, except under the following
        conditions:</p>

        <ul>
          <li>You may use the <a
          href="../../apache_pb.gif">'Powered by Apache'
          graphic</a> on a Web site that is being served by the
          Apache HTTP server software.</li>

          <li>You may use the aforementioned 'Powered by Apache'
          graphic or the <a
          href="http://www.apache.org/images/asf_logo.gif">
          Apache Software Foundation logo</a> in product
          description and promotional material <b>IF and ONLY
          IF</b> such use can in no way be interpreted as anything
          other than an attribution. Using the Apache name and
          artwork in a manner that implies endorsement of a product
          or service is <b>strictly forbidden</b>.</li>
        </ul>
        <hr />
      </li>
    </ol>
    
    
  </body>
</html>


    








      
      
    

    <h3>B. General Technical Questions</h3>

    <ol>
      <li>
        <a id="what2do" name="what2do"><strong>"Why can't I ...?
        Why won't ... work?" What to do in case of
        problems</strong></a> 

        <p>If you are having trouble with your Apache server
        software, you should take the following steps:</p>

        <ol>
          <li>
            <strong>Check the errorlog!</strong> 

            <p>Apache tries to be helpful when it encounters a
            problem. In many cases, it will provide some details by
            writing one or messages to the server error log.
            Sometimes this is enough for you to diagnose &amp; fix
            the problem yourself (such as file permissions or the
            like). The default location of the error log is
            <samp>/usr/local/apache/logs/error_log</samp>, but see
            the <a
            href="../mod/core.html#errorlog"><samp>ErrorLog</samp></a>
            directive in your config files for the location on your
            server.</p>
          </li>

          <li>
            <strong>Check the <a
            href="http://httpd.apache.org/docs/misc/FAQ.html">FAQ</a>!</strong>
            

            <p>The latest version of the Apache Frequently-Asked
            Questions list can always be found at the main Apache
            web site.</p>
          </li>

          <li>
            <strong>Check the Apache bug database</strong> 

            <p>Most problems that get reported to The Apache Group
            are recorded in the <a
            href="http://bugs.apache.org/">bug database</a>.
            <em><strong>Please</strong> check the existing reports,
            open <strong>and</strong> closed, before adding
            one.</em> If you find that your issue has already been
            reported, please <em>don't</em> add a "me, too" report.
            If the original report isn't closed yet, we suggest
            that you check it periodically. You might also consider
            contacting the original submitter, because there may be
            an email exchange going on about the issue that isn't
            getting recorded in the database.</p>
          </li>

          <li>
            <strong>Ask in a user support group.</strong> 

            <p>A lot of common problems never make it to the bug
            database because there's already high Q&amp;A traffic
            about them in the <a
            href="http://httpd.apache.org/userslist.html">Users
            mailing list</a> or <a
            href="news:comp.infosystems.www.servers.unix"><samp>comp.infosystems.www.servers.unix</samp></a>
            and related newsgroups. These newsgroups are also
            available via <a
            href="http://groups.google.com/groups?group=comp.infosystems.www.servers">
            Google</a>. Many Apache users, and some of the developers,
            can be found roaming their virtual halls, so it is suggested
            that you seek wisdom there. The chances are good that
            you'll get a faster answer there than from the bug
            database, even if you <em>don't</em> see your question
            already posted.</p>
          </li>

          <li>
            <strong>If all else fails, report the problem in the
            bug database</strong> 

            <p>If you've gone through those steps above that are
            appropriate and have obtained no relief, then please
            <em>do</em> let The Apache Group know about the problem
            by <a
            href="http://httpd.apache.org/bug_report.html">logging
            a bug report</a>.</p>

            <p>If your problem involves the server crashing and
            generating a core dump, please include a backtrace (if
            possible). As an example,</p>

            <dl>
              <dd><code># cd <em>ServerRoot</em><br />
               # dbx httpd core<br />
               (dbx) where</code></dd>
            </dl>

            <p>(Substitute the appropriate locations for your
            <samp>ServerRoot</samp> and your <samp>httpd</samp> and
            <samp>core</samp> files. You may have to use
            <code>gdb</code> instead of <code>dbx</code>.)</p>
          </li>
        </ol>
        <hr />
      </li>

      <li>
        <a id="compatible" name="compatible"><strong>How compatible
        is Apache with my existing NCSA 1.3 setup?</strong></a> 

        <p>Apache attempts to offer all the features and
        configuration options of NCSA httpd 1.3, as well as many of
        the additional features found in NCSA httpd 1.4 and NCSA
        httpd 1.5.</p>

        <p>NCSA httpd appears to be moving toward adding
        experimental features which are not generally required at
        the moment. Some of the experiments will succeed while
        others will inevitably be dropped. The Apache philosophy is
        to add what's needed as and when it is needed.</p>

        <p>Friendly interaction between Apache and NCSA developers
        should ensure that fundamental feature enhancements stay
        consistent between the two servers for the foreseeable
        future.</p>
        <hr />
      </li>

      <li>
        <a id="year2000" name="year2000"><strong>Is Apache Year
        2000 compliant?</strong></a> 

        <p>Yes, Apache is Year 2000 compliant.</p>

        <p>Apache internally never stores years as two digits. On
        the HTTP protocol level RFC1123-style addresses are
        generated which is the only format a HTTP/1.1-compliant
        server should generate. To be compatible with older
        applications Apache recognizes ANSI C's
        <code>asctime()</code> and RFC850-/RFC1036-style date
        formats, too. The <code>asctime()</code> format uses
        four-digit years, but the RFC850 and RFC1036 date formats
        only define a two-digit year. If Apache sees such a date
        with a value less than 70 it assumes that the century is
        <samp>20</samp> rather than <samp>19</samp>.</p>

        <p>Although Apache is Year 2000 compliant, you may still
        get problems if the underlying OS has problems with dates
        past year 2000 (<em>e.g.</em>, OS calls which accept or
        return year numbers). Most (UNIX) systems store dates
        internally as signed 32-bit integers which contain the
        number of seconds since 1<sup>st</sup> January 1970, so the
        magic boundary to worry about is the year 2038 and not
        2000. But modern operating systems shouldn't cause any
        trouble at all.</p>

        <p>Users of Apache 1.2.x should upgrade to a current
        version of Apache 1.3 (see <a
        href="../new_features_1_3.html#misc">year-2000 improvements
        in Apache 1.3</a> for details).</p>

        <p>The Apache HTTP Server project is an open-source
        software product of the Apache Software Foundation. The
        project and the Foundation <b>cannot</b> offer legal
        assurances regarding any suitability of the software for
        your application. There are several commercial Apache
        support organizations and derivative server products
        available that may be able to stand behind the software and
        provide you with any assurances you may require. You may
        find links to some of these vendors at <samp>&lt;<a
        href="http://www.apache.org/info/support.cgi">http://www.apache.org/info/support.cgi</a>&gt;</samp>.</p>

        <p>The Apache HTTP server software is distributed with the
        following disclaimer, found in the software license:</p>
<pre>
   THIS SOFTWARE IS PROVIDED BY THE APACHE GROUP ``AS IS'' AND ANY
   EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
   IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
   PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE APACHE GROUP OR
   ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
   NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
   LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
   HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
   OF THE POSSIBILITY OF SUCH DAMAGE.
 
</pre>
        <hr />
      </li>

      <li>
        <a id="submit_patch" name="submit_patch"><strong>How do I
        submit a patch to the Apache Group?</strong></a> 

        <p>The Apache Group encourages patches from outside
        developers. There are 2 main "types" of patches: small
        bugfixes and general improvements. Bugfixes should be
        submitting using the Apache <a
        href="http://httpd.apache.org/bug_report.html">bug report
        page</a>. Improvements, modifications, and additions should
        follow the instructions below.</p>

        <p>In general, the first course of action is to be a member
        of the <samp>dev@httpd.apache.org</samp> mailing list. This
        indicates to the Group that you are closely following the
        latest Apache developments. Your patch file should be
        generated using either '<code>diff&nbsp;-c</code>' or
        '<code>diff&nbsp;-u</code>' against the latest CVS tree. To
        submit your patch, send email to
        <samp>dev@httpd.apache.org</samp> with a
        <samp>Subject:</samp> line that starts with
        <samp>[PATCH]</samp> and includes a general description of
        the patch. In the body of the message, the patch should be
        clearly described and then included at the end of the
        message. If the patch-file is long, you can note a URL to
        the file instead of the file itself. Use of MIME
        enclosures/attachments should be avoided.</p>

        <p>Be prepared to respond to any questions about your
        patches and possibly defend your code. If your patch
        results in a lot of discussion, you may be asked to submit
        an updated patch that incorporate all changes and
        suggestions.</p>
        <hr />
      </li>

      <li>
        <a id="domination" name="domination"><strong>Why has Apache
        stolen my favourite site's Internet address?</strong></a> 

        <p>The simple answer is: "It hasn't." This misconception is
        usually caused by the site in question having migrated to
        the Apache Web server software, but not having migrated the
        site's content yet. When Apache is installed, the default
        page that gets installed tells the Webmaster the
        installation was successful. The expectation is that this
        default page will be replaced with the site's real content.
        If it doesn't, complain to the Webmaster, not to the Apache
        project -- we just make the software and aren't responsible
        for what people do (or don't do) with it.</p>
        <hr />
      </li>

      <li>
        <a id="apspam" name="apspam"><strong>Why am I getting spam
        mail from the Apache site?</strong></a> 

        <p>The short answer is: "You aren't." Usually when someone
        thinks the Apache site is originating spam, it's because
        they've traced the spam to a Web site, and the Web site
        says it's using Apache. See the <a
        href="#domination">previous FAQ entry</a> for more details
        on this phenomenon.</p>

        <p>No marketing spam originates from the Apache site. The
        only mail that comes from the site goes only to addresses
        that have been <em>requested</em> to receive the mail.</p>
        <hr />
      </li>

      <li>
        <a id="redist" name="redist"><strong>May I include the
        Apache software on a CD or other package I'm
        distributing?</strong></a> 

        <p>The detailed answer to this question can be found in the
        Apache license, which is included in the Apache
        distribution in the file <code>LICENSE</code>. You can also
        find it on the Web at <samp>&lt;<a
        href="http://www.apache.org/LICENSE.txt">http://www.apache.org/LICENSE.txt</a>&gt;</samp>.</p>
        <hr />
      </li>

      <li>
        <a id="zoom" name="zoom"><strong>What's the best
        hardware/operating system/... How do I get the most out of
        my Apache Web server?</strong></a> 

        <p>Check out Dean Gaudet's <a
        href="perf-tuning.html">performance tuning page</a>.</p>
        <hr />
      </li>

      <li>
        <a id="regex" name="regex"><strong>What are "regular
        expressions"?</strong></a> 

        <p>Regular expressions are a way of describing a pattern -
        for example, "all the words that begin with the letter A"
        or "every 10-digit phone number" or even "Every sentence
        with two commas in it, and no capital letter Q". Regular
        expressions (aka "regex"s) are useful in Apache because
        they let you apply certain attributes against collections
        of files or resources in very flexible ways - for example,
        all .gif and .jpg files under any "images" directory could
        be written as /\/images\/.*(jpg|gif)$/.</p>

        <p>The best overview around is probably the one which comes
        with Perl. We implement a simple subset of Perl's regex
        support, but it's still a good way to learn what they mean.
        You can start by going to the <a
        href="http://www.perl.com/CPAN-local/doc/manual/html/pod/perlre.html#Regular_Expressions">
        CPAN page on regular expressions</a>, and branching out
        from there.</p>
        <hr />
      </li>

      <li>
        <a id="binaries" name="binaries"><b>Why isn't there a
        binary for my platform?</b></a> 

        <p>The developers make sure that the software builds and
        works correctly on the platforms available to them; this
        does <i>not</i> necessarily mean that <i>your</i> platform
        is one of them. In addition, the Apache HTTP server project
        is primarily source oriented, meaning that distributing
        valid and buildable source code is the purpose of a
        release, not making sure that there is a binary package for
        all of the supported platforms.</p>

        <p>If you don't see a kit for your platform listed in the
        binary distribution area (&lt;URL:<a
        href="http://httpd.apache.org/dist/httpd/binaries/">http://httpd.apache.org/dist/httpd/binaries/</a>&gt;),
        it means either that the platform isn't available to any of
        the developers, or that they just haven't gotten around to
        preparing a binary for it. As this is a voluntary project,
        they are under no obligation to do so. Users are encouraged
        and expected to build the software themselves.</p>

        <p>The sole exception to these practices is the Windows
        package. Unlike most Unix and Unix-like platforms, Windows
        systems do not come with a bundled software development
        environment, so we <i>do</i> prepare binary kits for
        Windows when we make a release. Again, however, it's a
        voluntary thing and only a limited number of the developers
        have the capability to build the InstallShield package, so
        the Windows release may lag somewhat behind the source
        release. This lag should be no more than a few days at
        most.</p>
        <hr />
      </li>
    </ol>
    
    
  </body>
</html>


    








      
      
    

    <h3>C. Building Apache</h3>

    <ol>
      <li>
        <a id="bind8.1" name="bind8.1"><strong>Why do I get an
        error about an undefined reference to
        "<samp>__inet_ntoa</samp>" or other <samp>__inet_*</samp>
        symbols?</strong></a> 

        <p>If you have installed <a
        href="http://www.isc.org/bind.html">BIND-8</a> then this is
        normally due to a conflict between your include files and
        your libraries. BIND-8 installs its include files and
        libraries <code>/usr/local/include/</code> and
        <code>/usr/local/lib/</code>, while the resolver that comes
        with your system is probably installed in
        <code>/usr/include/</code> and <code>/usr/lib/</code>. If
        your system uses the header files in
        <code>/usr/local/include/</code> before those in
        <code>/usr/include/</code> but you do not use the new
        resolver library, then the two versions will conflict.</p>

        <p>To resolve this, you can either make sure you use the
        include files and libraries that came with your system or
        make sure to use the new include files and libraries.
        Adding <code>-lbind</code> to the
        <code>EXTRA_LDFLAGS</code> line in your
        <samp>Configuration</samp> file, then re-running
        <samp>Configure</samp>, should resolve the problem. (Apache
        versions 1.2.* and earlier use <code>EXTRA_LFLAGS</code>
        instead.)</p>

        <p><strong>Note:</strong>As of BIND 8.1.1, the bind
        libraries and files are installed under
        <samp>/usr/local/bind</samp> by default, so you should not
        run into this problem. Should you want to use the bind
        resolvers you'll have to add the following to the
        respective lines:</p>

        <dl>
          <dd><code>EXTRA_CFLAGS=-I/usr/local/bind/include<br />
           EXTRA_LDFLAGS=-L/usr/local/bind/lib<br />
           EXTRA_LIBS=-lbind</code></dd>
        </dl>
        <hr />
      </li>

      <li>
        <a id="cantbuild" name="cantbuild"><strong>Why won't Apache
        compile with my system's <samp>cc</samp>?</strong></a> 

        <p>If the server won't compile on your system, it is
        probably due to one of the following causes:</p>

        <ul>
          <li><strong>The <samp>Configure</samp> script doesn't
          recognize your system environment.</strong><br />
           This might be either because it's completely unknown or
          because the specific environment (include files, OS
          version, <em>et cetera</em>) isn't explicitly handled. If
          this happens, you may need to port the server to your OS
          yourself.</li>

          <li><strong>Your system's C compiler is
          garbage.</strong><br />
           Some operating systems include a default C compiler that
          is either not ANSI C-compliant or suffers from other
          deficiencies. The usual recommendation in cases like this
          is to acquire, install, and use <samp>gcc</samp>.</li>

          <li><strong>Your <samp>include</samp> files may be
          confused.</strong><br />
           In some cases, we have found that a compiler
          installation or system upgrade has left the C header
          files in an inconsistent state. Make sure that your
          include directory tree is in sync with the compiler and
          the operating system.</li>

          <li><strong>Your operating system or compiler may be out
          of revision.</strong><br />
           Software vendors (including those that develop operating
          systems) issue new releases for a reason; sometimes to
          add functionality, but more often to fix bugs that have
  …
Large files files are truncated, but you can click here to view the full file