You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by Paul Richards <pa...@hyperreal.com> on 1996/11/17 21:34:34 UTC
cvs commit: apache/docs LICENSE client_block_api.html mod_fastcgi.html mod_usertrack.html windoz_keepalive.html xssi.html FAQ.html bind.html compat_notes.html core.html directives.html handler.html host.html index.html known_bugs.html mod_actions.html mod_alias.html mod_auth_dbm.html mod_cern_meta.html mod_env.html mod_info.html mod_mime.html mod_negotiation.html mod_proxy.html mod_status.html mod_userdir.html modules.html perf-bsd44.html perf.html virtual-host.html
paul 96/11/17 12:34:33
Modified: docs FAQ.html bind.html compat_notes.html core.html
directives.html handler.html host.html index.html
known_bugs.html mod_actions.html mod_alias.html
mod_auth_dbm.html mod_cern_meta.html mod_env.html
mod_info.html mod_mime.html mod_negotiation.html
mod_proxy.html mod_status.html mod_userdir.html
modules.html perf-bsd44.html perf.html
virtual-host.html
Added: docs LICENSE client_block_api.html mod_fastcgi.html
mod_usertrack.html windoz_keepalive.html xssi.html
Log:
Update docs to current (1.2)
Revision Changes Path
1.2 +35 -138 apache/docs/FAQ.html
Index: FAQ.html
===================================================================
RCS file: /export/home/cvs/apache/docs/FAQ.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** FAQ.html 1996/11/17 20:22:37 1.1
--- FAQ.html 1996/11/17 20:34:06 1.2
***************
*** 12,26 ****
<OL>
<LI><A HREF="#what">What is Apache ?</A>
<LI><A HREF="#why">Why was Apache created ?</A>
! <LI><A HREF="#relate">How does the Apache group relate to the NCSA 1.4+ effort ?</A>
<LI><A HREF="#name">Why the name "Apache" ?</A>
<LI><A HREF="#compatible">How compatible is Apache with my existing NCSA 1.3 setup ?</A>
- <LI><A HREF="#wait">Why didn't the Apache group wait for NCSA 1.4 ?</A>
<LI><A HREF="#compare">OK, so how does Apache compare to other servers ?</A>
<LI><A HREF="#tested">How thoroughly tested is Apache?</A>
- <LI><A HREF="#extensions">What extensions does Apache offer over NCSA 1.x?</A>
<LI><A HREF="#proxy">Does or will Apache act as a Proxy server?</A>
- <LI><A HREF="#bugs">What NCSA 1.3 bugs are fixed in Apache ?</A>
<LI><A HREF="#future">What are the future plans for Apache ?</A>
<LI><A HREF="#support">Who do I contact for support ?</A>
<LI><A HREF="#more">Is there any more information on Apache ?</A>
--- 12,23 ----
<OL>
<LI><A HREF="#what">What is Apache ?</A>
<LI><A HREF="#why">Why was Apache created ?</A>
! <LI><A HREF="#relate">How does the Apache group relate to other servers ?</A>
<LI><A HREF="#name">Why the name "Apache" ?</A>
<LI><A HREF="#compatible">How compatible is Apache with my existing NCSA 1.3 setup ?</A>
<LI><A HREF="#compare">OK, so how does Apache compare to other servers ?</A>
<LI><A HREF="#tested">How thoroughly tested is Apache?</A>
<LI><A HREF="#proxy">Does or will Apache act as a Proxy server?</A>
<LI><A HREF="#future">What are the future plans for Apache ?</A>
<LI><A HREF="#support">Who do I contact for support ?</A>
<LI><A HREF="#more">Is there any more information on Apache ?</A>
***************
*** 37,64 ****
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. 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.
</P>
<HR>
! <LI><A name="relate">How does the Apache group relate to the NCSA 1.4 effort ?</A>
<P>
! 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.
</P>
<HR>
<LI><A name="why">Why was Apache created ?</A>
<P>to address concerns of a group of www providers and part time httpd
! programmers, that httpd didn't behave as they wanted it to.
</P>
<HR>
--- 34,62 ----
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>Since it began, it has been completely rewritten, and includes many new
! features. Apache is, as of June 1996, the most popular WWW server on
! the Internet, according to the <a
! href="http://www.netcraft.com/Survey/">Netcraft Survey</a>.
!
</P>
<HR>
! <LI><A name="relate">How does the Apache group relate to other
! server efforts, such as NCSA's?</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
! entitely independent venture.
</P>
<HR>
<LI><A name="why">Why was Apache created ?</A>
<P>to address concerns of a group of www providers and part time httpd
! programmers, that httpd didn't behave as they wanted it
! to. Apache is an entirely volunteer effort, completely funded by its
! members, not by commercial sales.
</P>
<HR>
***************
*** 88,191 ****
<HR>
- <LI><A name="wait">Why didn't the Apache group wait for NCSA 1.4 ?</A>
- <P>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 free server. With its collaborative development team we
- openly welcome new volunteers, suggestions and support.
- </P>
- <HR>
-
<LI><A name="compare">OK, so how does Apache compare to other servers ?</A>
<P>
For an independent assessment, see <A HREF="http://www.webcompare.com/server-main.html">http://www.webcompare.com/server-main.html</A>
</P>
! <!-- <P>
! Regarding features, Apache supports more flexibility in custom
! error responses; it also has DBM databases, and content negotiation,
! which aren't in the NCSA code... yet.
! </P>
! <P>
! As to performance, both offer a substantial performance boost over
! NCSA 1.3. On systems where it is capable of fork-free operation,
! early beta versions of NCSA 1.4 clock in about twice as fast as
! Apache for simple file retrievals. However, this test involved an
! early release of the NCSA software, and that ratio may change
! either way between now and final release. Also, if your server
! spends a lot of its CPU cycles running CGI scripts, or the like,
! your mileage may vary.
! </P> -->
<HR>
<LI><A name="tested">How thoroughly tested is Apache?</A>
- <P>
- Version 1.0 of Apache was 'plugged in' at,
- </P>
- <DL>
- <DT>www.hotwired.com</DT>
- <DD>IRIX.<BR>Hits/day 400,000+</DD>
- <DT>us.imdb.com</DT>
- <DD>FreeBSD.<BR>Hits/day 800,000+</DD>
- <DT>www.ai.mit.edu</DT>
- <DD>SunOS.<BR>Hits/day 100,000+</DD>
- <DT>www.hyperreal.com</DT>
- <DD>BSDI.<BR>Hits/day 40,000+</DD>
- </DL>
! <P><I>Also tested under HP-UX, Linux, SCO, Solaris, NeXT, .....</I></P>
! <P>See <A HREF="../info/apache_users.html">http://www.apache.org/info/apache_users.html</A> for an incomplete list of sites running Apache.</P>
! <P>
! 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.
! </P>
! <HR>
! <LI><A name=extensions>What extensions does Apache offer over NCSA 1.3 ?</A></P>
! <P>Here are just <B>some</B> of the new features...</P>
! <DL>
! <DT>Four ways of customizing error responses</DT>
! <DD><P>hard-coded responses, customizable text responses, local URL redirection, external URL redirection.</P></DD>
!
! <DT>Virtual-home</DT>
! <DD><P>A server running on a machine with multiple IP addresses can have a different <I>home page</I> for each IP address</P></DD>
!
! <DT>Additional CGI variables</DT>
! <DD><P>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.</P>
! </DD>
!
! <DT>Content negotiation</DT>
! <DD><P>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.
! </P><P>
! 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.
! </P>
! </DD>
! <DT>XBITHACK Last-modified:</DT>
! <DD><P>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.</P>
! </DD>
!
! <DT>Better CGI script control</DT>
! <DD><P>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,</P>
! <PRE>
! Status 404: URL was not found
! </PRE>
! </DD>
! <DT>Improved logging of redirected URLs</DT>
! <DD><P>If a request results in a redirect to another URL, both URLs are logged in
! the access_log</P></DD>
! <DT>Multiple <B>DirectoryIndex</B> filenames</DT>
! <DD><P>Apache will search for <B>index.html</B> as well as any other filenames you prefer.</P>
! </DL>
! <HR>
<LI><A name="proxy">Does or will Apache act as a Proxy server?
<p>Apache version 1.1
--- 86,118 ----
<HR>
<LI><A name="compare">OK, so how does Apache compare to other servers ?</A>
<P>
For an independent assessment, see <A HREF="http://www.webcompare.com/server-main.html">http://www.webcompare.com/server-main.html</A>
</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><A name="tested">How thoroughly tested is Apache?</A>
! <p>Apache is run on over 100,000 Internet servers (as of July 1996). 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 third of all
! WWW servers. When bugs do show up, we release patches and new
! versions, as soon as they are available.</a>
+ <P>See <A HREF="../info/apache_users.html">http://www.apache.org/info/apache_users.html</A> for an incomplete list of sites running Apache.</P>
! <hr>
<LI><A name="proxy">Does or will Apache act as a Proxy server?
<p>Apache version 1.1
***************
*** 194,229 ****
<p>
<HR>
- <LI><A name="bugs">What NCSA 1.3 bugs are fixed in Apache ?</A></P>
- <OL>
- <LI><B>Efficiency</B>...no longer does initgroups()
- or open_locale() on every connection, no longer does single-
- character read() system calls *ever*.<BR><BR>
- </LI>
-
- <LI>Fixed a condition that was leading to un-killable httpd
- processes piling up on server machines and chewing up swap space.<BR><BR>
- </LI>
-
- <LI>Unlimited numbers of Aliases and Redirects are allowed.<BR><BR></LI>
-
- <LI>AddTypes for the CGI and SERVER_INCLUDES magic MIME types are
- honored in .htaccess files.<BR><BR></LI>
-
- <LI>Auth_user is correctly logged for password-protected documents
- with server-side includes.<BR><BR></LI>
-
- <LI>Scripts can return Content-types with embedded blanks.<BR><BR></LI>
-
- <LI>Security hole allowing cgi script sources to be viewed, removed.<BR><BR></LI>
-
- <LI>Handling of redirects from scripts improved (no more mandatory
- three-second pauses on imagemap hits).<BR><BR></LI>
-
- <LI>XBITHACK also checks X-bits of included files.<BR><BR></LI>
- </OL>
- <HR>
-
<LI><A name="future">What are the future plans for Apache ?</A>
<P><UL>
<LI>to continue as a public domain HTTP server,
--- 121,126 ----
***************
*** 236,242 ****
<LI><A name="support">Who do I contact for support ?</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 to <A HREF="mailto:apache-bugs@mail.apache.org">apache-bugs@mail.apache.org</A>
Other questions should be directed to
<A HREF="news:comp.infosystems.www.servers.unix">comp.infosystems.www.servers.unix</A>, where some of the Apache team lurk,
in the company of many other httpd gurus who should be able
--- 133,139 ----
<LI><A name="support">Who do I contact for support ?</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 via <A HREF="http://www.apache.org/bug_report.html">the bug report page.</A>
Other questions should be directed to
<A HREF="news:comp.infosystems.www.servers.unix">comp.infosystems.www.servers.unix</A>, where some of the Apache team lurk,
in the company of many other httpd gurus who should be able
1.2 +7 -7 apache/docs/bind.html
Index: bind.html
===================================================================
RCS file: /export/home/cvs/apache/docs/bind.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** bind.html 1996/11/17 20:27:00 1.1
--- bind.html 1996/11/17 20:34:07 1.2
***************
*** 2,8 ****
<title>Setting which addresses and ports Apache uses</title>
</head><body>
! <img src="../../images/apache_sub.gif" alt="">
<h1>Setting which addresses and ports Apache uses</h1>
<hr>
--- 2,8 ----
<title>Setting which addresses and ports Apache uses</title>
</head><body>
! <img src="../images/apache_sub.gif" alt="">
<h1>Setting which addresses and ports Apache uses</h1>
<hr>
***************
*** 86,102 ****
<h2>See also</h2>
See also the documentation on
! <a href="../virtual-host.html">Virtual Hosts</a>,
<a href="host.html">Non-IP virtual hosts</a>,
! <a href="../core.html#bindaddress">BindAddress directive</a>,
! <a href="../core.html#port">Port directive</a>
and
! <a href="../core.html#virtualhost"><VirtualHost> section</a>.
</ul>
<hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="../"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 86,102 ----
<h2>See also</h2>
See also the documentation on
! <a href="virtual-host.html">Virtual Hosts</a>,
<a href="host.html">Non-IP virtual hosts</a>,
! <a href="core.html#bindaddress">BindAddress directive</a>,
! <a href="core.html#port">Port directive</a>
and
! <a href="core.html#virtualhost"><VirtualHost> section</a>.
</ul>
<hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +9 -0 apache/docs/compat_notes.html
Index: compat_notes.html
===================================================================
RCS file: /export/home/cvs/apache/docs/compat_notes.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** compat_notes.html 1996/11/17 20:22:39 1.1
--- compat_notes.html 1996/11/17 20:34:08 1.2
***************
*** 47,52 ****
--- 47,61 ----
<P>
+ <LI><CODE>AuthUserFile</CODE> requires a full pathname. In earlier
+ versions of NCSA httpd and Apache, you could use a filename
+ relative to the .htaccess file. This could be a major security hole,
+ as it made it trivially easy to make a ".htpass" file in the a
+ directory easily accessable by the world. We recommend you store
+ your passwords outside your document tree.
+
+ <P>
+
<LI><CODE>OldScriptAlias</CODE> is no longer supported.
<P>
1.2 +121 -7 apache/docs/core.html
Index: core.html
===================================================================
RCS file: /export/home/cvs/apache/docs/core.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** core.html 1996/11/17 20:22:40 1.1
--- core.html 1996/11/17 20:34:09 1.2
***************
*** 27,34 ****
<li><A HREF="#errordocument">ErrorDocument</A>
<li><A HREF="#errorlog">ErrorLog</A>
<li><A HREF="#group">Group</A>
! <li><A HREF="#identitycheck">IdentityCheck</A>
<li><A HREF="#limit"><Limit></A>
<li><A HREF="#maxclients">MaxClients</A>
<li><A HREF="#maxrequestsperchild">MaxRequestsPerChild</A>
<li><A HREF="#maxspareservers">MaxSpareServers</A>
--- 27,37 ----
<li><A HREF="#errordocument">ErrorDocument</A>
<li><A HREF="#errorlog">ErrorLog</A>
<li><A HREF="#group">Group</A>
! <li><A HREF="#keepalive">KeepAlive</A>
! <li><A HREF="#keepalivetimeout">KeepAliveTimeout</A>
<li><A HREF="#limit"><Limit></A>
+ <li><A HREF="#listen">Listen;</A>
+ <li><A HREF="#location"><Location></A>
<li><A HREF="#maxclients">MaxClients</A>
<li><A HREF="#maxrequestsperchild">MaxRequestsPerChild</A>
<li><A HREF="#maxspareservers">MaxSpareServers</A>
***************
*** 39,45 ****
--- 42,50 ----
<li><A HREF="#require">require</A>
<li><A HREF="#resourceconfig">ResourceConfig</A>
<li><A HREF="#serveradmin">ServerAdmin</A>
+ <li><A HREF="#serveralias">ServerAlias</A>
<li><A HREF="#servername">ServerName</A>
+ <li><A HREF="#serverpath">ServerPath</A>
<li><A HREF="#serverroot">ServerRoot</A>
<li><A HREF="#servertype">ServerType</A>
<li><A HREF="#startservers">StartServers</A>
***************
*** 204,209 ****
--- 209,217 ----
<A HREF="virtual-host.html">virtual hosts</A> instead of using
<A HREF="#virtualhost"><VirtualHost></A> sections.<p><hr>
+ <p><strong>See Also:</strong>
+ <a href="bind.html">Setting which addresses and ports Apache uses</a></p>
+
<A name="defaulttype"><h2>DefaultType directive</h2></A>
<!--%plaintext <?INDEX {\tt DefaultType} directive> -->
<strong>Syntax:</strong> DefaultType <em>mime-type</em><br>
***************
*** 247,253 ****
<blockquote><code>
<Directory /><br>
AllowOverride None<br>
! </Directory><br><br>
<Directory /home/*><br>
AllowOverride FileInfo<br>
</Directory></code></blockquote>
--- 255,261 ----
<blockquote><code>
<Directory /><br>
AllowOverride None<br>
! </Directoy><br><br>
<Directory /home/*><br>
AllowOverride FileInfo<br>
</Directory></code></blockquote>
***************
*** 291,297 ****
<A name="errordocument"><h2>ErrorDocument directive</h2></A>
<!--%plaintext <?INDEX {\tt ErrorDocument} directive> -->
<strong>Syntax:</strong> ErrorDocument <em>error-code document</em><br>
! <strong>Context</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
In the event of a problem or error, Apache can be configured to do
--- 299,305 ----
<A name="errordocument"><h2>ErrorDocument directive</h2></A>
<!--%plaintext <?INDEX {\tt ErrorDocument} directive> -->
<strong>Syntax:</strong> ErrorDocument <em>error-code document</em><br>
! <strong>Context</strong> server config, virtual host, directory, .htaccess<br>
<strong>Status:</strong> core<p>
In the event of a problem or error, Apache can be configured to do
***************
*** 370,376 ****
<!--%plaintext <?INDEX {\tt IdentityCheck} directive> -->
<strong>Syntax:</strong> IdentityCheck <em>boolean</em><br>
<strong>Default:</strong> <code>IdentityCheck off</code><br>
! <strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
This directive enables RFC931-compliant logging of the remote user name
--- 378,384 ----
<!--%plaintext <?INDEX {\tt IdentityCheck} directive> -->
<strong>Syntax:</strong> IdentityCheck <em>boolean</em><br>
<strong>Default:</strong> <code>IdentityCheck off</code><br>
! <strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
<strong>Status:</strong> core<p>
This directive enables RFC931-compliant logging of the remote user name
***************
*** 381,386 ****
--- 389,434 ----
The information should not trusted in any way except for rudimentary usage
tracking.<p><hr>
+ <h2><a name="keepalive">KeepAlive</a></h2>
+ <strong>Syntax:</strong> KeepAlive <em>max-requests</em><br>
+ <strong>Default:</strong> <code>KeepAlive 5</code><br>
+ <strong>Context:</strong> server config<br>
+ <strong>Status:</strong> Core<p>
+
+ This directive enables
+ <a href="keepalive.html">Keep-Alive</a>
+ support. Set <em>max-requests</em>
+ to the maximum number of requests you want Apache to entertain per
+ request. A limit is imposed to prevent a client from hogging your
+ server resources. Set this to <code>0</code> to disable support.
+
+ <h2><a name="keepalivetimeout">KeepAliveTimeout</a></h2>
+ <strong>Syntax:</strong> KeepAliveTimeout <em>seconds</em><br>
+ <strong>Default:</strong> <code>KeepAliveTimeout 15</code><br>
+ <strong>Context:</strong> server config<br>
+ <strong>Status:</strong> Core<p>
+
+ The number of seconds Apache will wait for a subsequent request before
+ closing the connection. Once a request has been received, the timeout
+ value specified by the <a
+ href="../core.html#timeout"><code>Timeout</code></a> directive
+ applies.
+
+
+ <A name="listen"><h2>Listen</h2></A>
+ <strong>Syntax:</strong>
+ Listen [<em>IP address</em>:]<em>port number</em><br>
+ <strong>Context:</strong> server config<br>
+ <strong>Status:</strong> core<p>
+
+ <p>The Listen directive instructs Apache to listen to more than one IP
+ address or port; by default it responds to requests on all IP
+ interfaces, but only on the port given by the <a href="#port">Port</a>
+ directive.</p>
+
+ <p><strong>See Also</strong>:
+ <a href="bind.html">Setting which addresses and ports Apache uses</a></p>
+
<A name="limit"><h2><Limit> directive</h2></A>
<!--%plaintext <?INDEX {\tt Limit} section directive> -->
<strong>Syntax:</strong>
***************
*** 401,406 ****
--- 449,495 ----
If an access control directive appears outside a <Limit> directive,
then it applies to all access methods.<p><hr>
+ <h2><a name="location"><Location></a></h2>
+
+ <strong>Syntax:</strong> <Location <em>URL prefix</em>><br>
+ <strong>Context:</strong> server config, virtual host<br>
+ <strong>Status:</strong> core<br>
+
+ <p>The <Location> directive provides for access control by
+ URL. It is comprable to the <a
+ href="#directory"><Directory></a> directive, and
+ should be matched with a </Location> directive. Directives that
+ apply to the URL given should be listen
+ within. <code><Location></code> sections are processed in the
+ order they appear in the configuration file, after the
+ <Directory> sections and <code>.htaccess</code> files are
+ read.</p>
+
+ <p>Note that, due to the way HTTP functions, <em>URL prefix</em>
+ should, save for proxy requests, be of the form <code>/path/</code>,
+ and should not include the <code>http://servername</code>. It doesn't
+ neccessarily have to protect a directory (it can be an individual
+ file, or a number of files), and can include wildcards. In a wildcard
+ string, `?' matches any single character, and `*' matches any
+ sequences of characters.
+
+ <p>This functionality is especially useful when combined with the
+ <code><a href="mod_mime.html#sethandler">SetHandler</a></code>
+ directive. For example, to enable status requests, but allow them only
+ from browsers at foo.com, you might use:
+
+ <pre>
+ <Location /status>
+ SetHandler server-status
+ <Limit GET>
+ order deny,allow
+ deny from all
+ allow from .foo.com
+ </Limit>
+ </Location>
+ </pre>
+
+
<A name="maxclients"><h2>MaxClients directive</h2></A>
<!--%plaintext <?INDEX {\tt MaxClients} directive> -->
<strong>Syntax:</strong> MaxClients <em>number</em><br>
***************
*** 645,650 ****
--- 734,751 ----
<blockquote><code>ServerAdmin www-admin@foo.bar.com</code></blockquote>
as users do not always mention that they are talking about the server!<p><hr>
+ <A name="serveralias"><h2>ServerAlias directive</h2></A>
+
+ <strong>Syntax:</strong> ServerAlias <em>host1 host2 ...</em><br>
+ <strong>Context:</strong> virtual host<br>
+ <strong>Status:</strong> core<p>
+
+ The ServerAlias directive sets the alternate names for a host, for use
+ with
+ <a href="host.html">Host-header based virtual hosts</a>.
+
+ <p><hr>
+
<A name="servername"><h2>ServerName directive</h2></A>
<!--%plaintext <?INDEX {\tt ServerName} directive> -->
<strong>Syntax:</strong> ServerName <em>fully-qualified domain name</em><br>
***************
*** 659,664 ****
--- 760,774 ----
would be used if the canonical (main) name of the actual machine
were <code>monster.wibble.com</code>.<p><hr>
+ <A name="serverpath"><h2>ServerPath directive</h2></A>
+
+ <strong>Syntax:</strong> ServerPath <em>pathname</em><br>
+ <strong>Context:</strong> virtual host<br>
+ <strong>Status:</strong> core<p>
+
+ The ServerAlias directive sets the legacy URL pathname for a host, for
+ use with <a href="host.html">Host-header based virtual hosts</a>.
+
<A name="serverroot"><h2>ServerRoot directive</h2></A>
<!--%plaintext <?INDEX {\tt ServerRoot} directive> -->
<strong>Syntax:</strong> ServerRoot <em>directory-filename</em><br>
***************
*** 769,775 ****
<A name="virtualhost"><h2><VirtualHost> directive</h2></A>
<!--%plaintext <?INDEX {\tt VirtualHost} section directive> -->
! <strong>Syntax:</strong> <VirtualHost <em>addr</em>> ...
</VirtualHost> <br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Core. <p>
--- 879,885 ----
<A name="virtualhost"><h2><VirtualHost> directive</h2></A>
<!--%plaintext <?INDEX {\tt VirtualHost} section directive> -->
! <strong>Syntax:</strong> <VirtualHost <em>addr</em>[:<em>port</em>]> ...
</VirtualHost> <br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Core. <p>
***************
*** 803,810 ****
<A HREF="vif.info.txt">VIF</A> (for SunOS(TM) 4.1.x).<p>
<!--%hypertext -->
! See also <A HREF="virtual-host.html">information on Virtual Hosts.</A><p>
! <!--/%hypertext -->
<hr>
--- 913,924 ----
<A HREF="vif.info.txt">VIF</A> (for SunOS(TM) 4.1.x).<p>
<!--%hypertext -->
! <p><strong>See also:</strong>
! <A HREF="virtual-host.html">Information on Virtual Hosts.
! (multihome)</A><br>
! <strong>See also:</strong>
! <a href="host.html">Non-IP address-based Virtual Hosts</a>
! <!--/%hypertext --></p>
<hr>
1.2 +41 -1 apache/docs/directives.html
Index: directives.html
===================================================================
RCS file: /export/home/cvs/apache/docs/directives.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** directives.html 1996/11/17 20:22:41 1.1
--- directives.html 1996/11/17 20:34:10 1.2
***************
*** 7,27 ****
<BODY>
<IMG SRC="../images/apache_sub.gif" ALT="">
! <H1>Apache directives</h1>
<ul>
<li><A HREF="core.html#accessconfig">AccessConfig</A>
<li><A HREF="core.html#accessfilename">AccessFileName</A>
<li><A HREF="mod_dir.html#adddescription">AddDescription</A>
<li><A HREF="mod_mime.html#addencoding">AddEncoding</A>
<li><A HREF="mod_dir.html#addicon">AddIcon</A>
<li><A HREF="mod_dir.html#addiconbyencoding">AddIconByEncoding</A>
<li><A HREF="mod_dir.html#addiconbytype">AddIconByType</A>
<li><A HREF="mod_mime.html#addlanguage">AddLanguage</A>
<li><A HREF="mod_mime.html#addtype">AddType</A>
<li><A HREF="mod_log_agent.html#agentlog">AgentLog</A>
<li><A HREF="mod_access.html#allow">allow</A>
<li><A HREF="core.html#allowoverride">AllowOverride</A>
<li><A HREF="mod_auth_dbm.html#authdbmgroupfile">AuthDBMGroupFile</A>
<li><A HREF="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</A>
<li><A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A>
--- 7,38 ----
<BODY>
<IMG SRC="../images/apache_sub.gif" ALT="">
! <H1>Apache directives</H1>
<ul>
<li><A HREF="core.html#accessconfig">AccessConfig</A>
<li><A HREF="core.html#accessfilename">AccessFileName</A>
+ <li><A HREF="mod_actions.html#action">Action</A>
<li><A HREF="mod_dir.html#adddescription">AddDescription</A>
<li><A HREF="mod_mime.html#addencoding">AddEncoding</A>
+ <li><A HREF="mod_mime.html#addhandler">AddHandler</A>
<li><A HREF="mod_dir.html#addicon">AddIcon</A>
<li><A HREF="mod_dir.html#addiconbyencoding">AddIconByEncoding</A>
<li><A HREF="mod_dir.html#addiconbytype">AddIconByType</A>
<li><A HREF="mod_mime.html#addlanguage">AddLanguage</A>
<li><A HREF="mod_mime.html#addtype">AddType</A>
+ <li><A HREF="mod_alias.html#alias">Alias</A>
<li><A HREF="mod_log_agent.html#agentlog">AgentLog</A>
<li><A HREF="mod_access.html#allow">allow</A>
<li><A HREF="core.html#allowoverride">AllowOverride</A>
+ <li><A HREF="mod_auth_anon.html#anonymous">Anonymous</A>
+ <li><A HREF="mod_auth_anon.html#LogEmail">Anonymous_LogEmail</A>
+ <li><A HREF="mod_auth_anon.html#VerifyEmail">Anonymous_VerifyEmail</A>
+ <li><A HREF="mod_auth_anon.html#NoUser">Anonymous_NoUser</A>
+ <li><A HREF="mod_auth_anon.html#Authorative">Anonymous_Authorative</A>
+ <li><A HREF="mod_digest.html#authdigestfile">AuthDigestFile</A>
+ <li><A HREF="mod_auth_dbm.html#authdbgroupfile">AuthDBGroupFile</A>
+ <li><A HREF="mod_auth_dbm.html#authdbuserfile">AuthDBUserFile</A>
<li><A HREF="mod_auth_dbm.html#authdbmgroupfile">AuthDBMGroupFile</A>
<li><A HREF="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</A>
<li><A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A>
***************
*** 29,34 ****
--- 40,52 ----
<li><A HREF="core.html#authname">AuthName</A>
<li><A HREF="core.html#authtype">AuthType</A>
<li><A HREF="core.html#bindaddress">BindAdress</A>
+ <li><A HREF="mod_proxy.html#cachedefaultexpire">CacheDefaultExpire</A>
+ <li><A HREF="mod_proxy.html#cachegcinterval">CacheGcInterval</A>
+ <li><A HREF="mod_proxy.html#cachelastmodfied">CacheLastModified</A>
+ <li><A HREF="mod_proxy.html#cachemaxexpire">CacheMaxExpire</A>
+ <li><A HREF="mod_negotiation.html#cachenegotiateddocs">CacheNegotiatedDocs</A>
+ <li><A HREF="mod_proxy.html#cacheroot">CacheRoot</A>
+ <li><A HREF="mod_proxy.html#cachesize">CacheSize</A>
<li><A HREF="mod_cookies.html#cookielog">CookieLog</A>
<li><A HREF="mod_dir.html#defaulticon">DefaultIcon</A>
<li><A HREF="core.html#defaulttype">DefaultType</A>
***************
*** 39,71 ****
--- 57,111 ----
<li><A HREF="core.html#errordocument">ErrorDocument</A>
<li><A HREF="core.html#errorlog">ErrorLog</A>
<li><A HREF="mod_dir.html#fancyindexing">FancyIndexing</A>
+ <li><A HREF="mod_mime.html#forcetype">ForceType</A>
<li><A HREF="core.html#group">Group</A>
<li><A HREF="mod_dir.html#headername">HeaderName</A>
<li><A HREF="core.html#identitycheck">IdentityCheck</A>
+ <li><A HREF="mod_imap.html#imapbase">ImapBase</A>
+ <li><A HREF="mod_imap.html#imapdefault">ImapDefault</A>
+ <li><A HREF="mod_imap.html#imapmenu">ImapMenu</A>
<li><A HREF="mod_dir.html#indexignore">IndexIgnore</A>
<li><A HREF="mod_dir.html#indexoptions">IndexOptions</A>
+ <li><A HREF="core.html#keepalive">KeepAlive</A>
+ <li><A HREF="core.html#keepalivetimeout">KeepAliveTimeout</A>
<li><A HREF="mod_negotiation.html#languagepriority">LanguagePriority</A>
<li><A HREF="core.html#limit"><Limit></A>
+ <li><A HREF="core.html#listen">Listen</A>
<li><A HREF="mod_dld.html#loadfile">LoadFile</A>
<li><A HREF="mod_dld.html#loadmodule">LoadModule</A>
+ <li><A HREF="core.html#location"><Location></A>
<li><A HREF="mod_log_config.html#logformat">LogFormat</A>
<li><A HREF="core.html#maxclients">MaxClients</A>
<li><A HREF="core.html#maxrequestsperchild">MaxRequestsPerChild</A>
<li><A HREF="core.html#maxspareservers">MaxSpareServers</A>
+ <li><A HREF="mod_cern_meta.html#metadir">MetaDir</A>
+ <li><A HREF="mod_cern_meta.html#metasuffix">MetaSuffix</A>
<li><A HREF="core.html#minspareservers">MinSpareServers</A>
+ <li><A HREF="mod_proxy.html#nocache">NoCache</A>
<li><A HREF="core.html#options">Options</A>
<li><A HREF="mod_access.html#order">order</A>
+ <li><A HREF="mod_env.html#passenv">PassEnv</A>
<li><A HREF="core.html#pidfile">PidFile</A>
<li><A HREF="core.html#port">Port</A>
+ <li><A HREF="mod_proxy.html#proxyrequests">ProxyRequests</A>
+ <li><A HREF="mod_proxy.html#proxyremote">ProxyRemote</A>
+ <li><A HREF="mod_proxy.html#proxypass">ProxyPass</A>
<li><A HREF="mod_dir.html#readmename">ReadmeName</A>
<li><A HREF="mod_log_referer.html#refererignore">RefererIgnore</A>
<li><A HREF="mod_log_referer.html#refererlog">RefererLog</A>
<li><A HREF="core.html#require">require</A>
+ <li><A HREF="mod_alias.html#redirect">Redirect</A>
<li><A HREF="core.html#resourceconfig">ResourceConfig</A>
+ <li><A HREF="mod_actions.html#script">Script</A>
+ <li><A HREF="mod_alias.html#scriptalias">ScriptAlias</A>
<li><A HREF="core.html#serveradmin">ServerAdmin</A>
+ <li><A HREF="core.html#serveralias">ServerAlias</A>
<li><A HREF="core.html#servername">ServerName</A>
+ <li><A HREF="core.html#serverpath">ServerPath</A>
<li><A HREF="core.html#serverroot">ServerRoot</A>
<li><A HREF="core.html#servertype">ServerType</A>
+ <li><A HREF="mod_env.html#setenv">SetEnv</A>
+ <li><A HREF="mod_mime.html#sethandler">SetHandler</A>
<li><A HREF="core.html#startservers">StartServers</A>
<li><A HREF="core.html#timeout">TimeOut</A>
<li><A HREF="mod_log_common.html#transferlog">TransferLog</A> (mod_log_common)
1.2 +25 -11 apache/docs/handler.html
Index: handler.html
===================================================================
RCS file: /export/home/cvs/apache/docs/handler.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** handler.html 1996/11/17 20:27:00 1.1
--- handler.html 1996/11/17 20:34:10 1.2
***************
*** 5,11 ****
</HEAD>
<BODY>
! <IMG SRC="../../images/apache_sub.gif" ALT="">
<h1>Apache's Handler Use</h1>
<h2>What is a Handler</h2>
--- 5,11 ----
</HEAD>
<BODY>
! <IMG SRC="../images/apache_sub.gif" ALT="">
<h1>Apache's Handler Use</h1>
<h2>What is a Handler</h2>
***************
*** 29,41 ****
handlers in the standard distribution are as follows:</p>
<ul>
! <li><strong>send-as-is</strong>: Send file with HTTP headers as is.
! <li><strong>cgi-script</strong>: Treat the file as a CGI script.
! <li><strong>imap-file</strong>: Imagemap rule file.
! <li><strong>server-info</strong>: Get the server's configuration info
! <li><strong>server-parsed</strong>: Parse for server-side includes
! <li><strong>server-status</strong>: Get the server's status report
! <li><strong>type-map</strong>: Parse as a type map file for content negotation
</ul>
<p>
--- 29,55 ----
handlers in the standard distribution are as follows:</p>
<ul>
! <li><strong>send-as-is</strong>:
! Send file with HTTP headers as is.
! (<a href="mod_asis.html">mod_asis</a>)
! <li><strong>cgi-script</strong>:
! Treat the file as a CGI script.
! (<a href="mod_cgi.html">mod_cgi</a>)
! <li><strong>imap-file</strong>:
! Imagemap rule file.
! (<a href="mod_imap.html">mod_imap</a>)
! <li><strong>server-info</strong>:
! Get the server's configuration information
! (<a href="mod_info.html">mod_info</a>)
! <li><strong>server-parsed</strong>:
! Parse for server-side includes
! (<a href="mod_include.html">mod_include</a>)
! <li><strong>server-status</strong>:
! Get the server's status report
! (<a href="mod_status.html">mod_status</a>)
! <li><strong>type-map</strong>:
! Parse as a type map file for content negotation
! (<a href="mod_negotiation.html">mod_negotiation</a>)
</ul>
<p>
***************
*** 99,105 ****
<h2>Programmer's Note</h2>
<p>In order to implement the handler features, an addition has been
! made to the <a href="../API.html">Apache API</a> that you may wish to
make use of. Specifically, a new record has been added to the
<code>request_rec</code> structure:</p>
<pre>
--- 113,119 ----
<h2>Programmer's Note</h2>
<p>In order to implement the handler features, an addition has been
! made to the <a href="API.html">Apache API</a> that you may wish to
make use of. Specifically, a new record has been added to the
<code>request_rec</code> structure:</p>
<pre>
***************
*** 116,123 ****
<hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 130,137 ----
<hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +40 -9 apache/docs/host.html
Index: host.html
===================================================================
RCS file: /export/home/cvs/apache/docs/host.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** host.html 1996/11/17 20:27:01 1.1
--- host.html 1996/11/17 20:34:10 1.2
***************
*** 22,37 ****
to determine the hostname it is being addressed as, Apache's virtual
host support has required a seperate IP address for each
server. Documentation on using this approach (which still works very
! well) is available <a href="../virtual-host.html">here</a>.
<p>While the approach described above works, with the available IP
address space growing smaller, and the number of domains increasing,
it is not the most elegant solution, and is hard to implement on some
! machines. The <code>HTTP/1.1</code>
! protocol (which is still under construction as of this writing)
! contains a method for the server to identify what name it is being
! addressed as. Apache 1.1 and later support this approach as well as
! the traditional IP-address-per-hostname method.</p>
<p>The benefits of using the new virtual host support is a practically
unlimited number of servers, ease of configuration and use, and
--- 22,36 ----
to determine the hostname it is being addressed as, Apache's virtual
host support has required a seperate IP address for each
server. Documentation on using this approach (which still works very
! well) is available <a href="virtual-host.html">here</a>.
<p>While the approach described above works, with the available IP
address space growing smaller, and the number of domains increasing,
it is not the most elegant solution, and is hard to implement on some
! machines. The <code>HTTP/1.1</code> protocol contains a method for the
! server to identify what name it is being addressed as. Apache 1.1 and
! later support this approach as well as the traditional
! IP-address-per-hostname method.</p>
<p>The benefits of using the new virtual host support is a practically
unlimited number of servers, ease of configuration and use, and
***************
*** 41,49 ****
later) do, but many browsers, especially older ones, do not. This can
cause problems, although a possible solution is addressed below.</p>
! <hr>
!
! <h3>Using non-IP Virtual Hosts</h3>
<p>Using the new virtual hosts is quite easy, and superficially looks
like the old method. You simply add to one of the Apache configuration
--- 40,46 ----
later) do, but many browsers, especially older ones, do not. This can
cause problems, although a possible solution is addressed below.</p>
! <h2>Using non-IP Virtual Hosts</h2>
<p>Using the new virtual hosts is quite easy, and superficially looks
like the old method. You simply add to one of the Apache configuration
***************
*** 55,60 ****
--- 52,58 ----
DocumentRoot /usr/web/apache
</VirtualHost>
</pre>
+
<p>Of course, any additional directives can (and should) be placed
into the <code><VirtualHost></code> section. To make this work,
all that is needed is to make sure that the <code>www.apache.org</code>
***************
*** 70,80 ****
--- 68,111 ----
server. This is possible with the <code>ServerAlias</code>
directive, placed inside the <VirtualHost> section. For
example:</p>
+
<pre>
ServerAlias apache.org *.apache.org
</pre>
+
<p>Note that you can use <code>*</code> and <code>?</code> as wildcard
characters.</p>
+
+ <h2>Security Considerations</h2>
+
+ Apache allows all virtual hosts to be made accessible via the
+ <code>Host:</code> header through all IP interfaces, even those which
+ are configured to use different IP interfaces. For example, if the
+ configuration for <code>www.foo.com</code> contained a virtual host
+ section for <code>www.bar.com</code>, and <code>www.bar.com</code> was
+ a separate IP interface, such that
+ non-<code>Host:</code>-header-supporting browsers can use it, as
+ before with Apache 1.0. If a request is made to
+ <code>www.foo.com</code> and the request includes the header
+ <code>Host: www.bar.com</code>, a page from <code>www.bar.com</code>
+ will be sent.
+
+ <P>
+
+ This is a security concern if you are controlling access to a
+ particular server based on IP-layer controls, such as from within a
+ firewall or router. Let's say <code>www.bar.com</code> in the above
+ example was instead an intranet server called
+ <code>private.foo.com</code>, and the router used by foo.com only let
+ internal users access <code>private.foo.com</code>. Obviously,
+ <code>Host:</code> header functionality now allows someone who has
+ access to <code>www.foo.com</code> to get
+ <code>private.foo.com</code>, if they send a <code>Host:
+ private.foo.com</code> header. It is important to note that this
+ condition exists only if you only implement this policy at the IP
+ layer - all security controls used by Apache (i.e., <A
+ HREF="mod_access.html">allow, deny from,</A> etc.) are consistantly
+ respected.
<h2>Compatibility with Older Browsers</h2>
1.3 +127 -173 apache/docs/index.html
Index: index.html
===================================================================
RCS file: /export/home/cvs/apache/docs/index.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** index.html 1996/11/17 20:27:01 1.2
--- index.html 1996/11/17 20:34:11 1.3
***************
*** 1,5 ****
<html><head>
! <title>New features with Apache 1.1</title>
</head><body>
<img src="../../images/apache_sub.gif" alt="">
--- 1,5 ----
<html><head>
! <title>New features with Apache 1.2</title>
</head><body>
<img src="../../images/apache_sub.gif" alt="">
***************
*** 7,23 ****
<h2>API Changes</h2>
! A few changes to the Apache API were made for 1.1. It is possible
! that some third-party modules will no longer work with 1.1, though
! we have made every effort to provide backwards-compatibility. If you
! encounter a module that does not work with 1.1, please <a
! href="../../bug_report.html">let us know</a>.
!
! <h2>New Features with Apache 1.1</h2>
<p>New features with this release, as extensions of the Apache
! functionality (see also more detailed <code>CHANGES</code> file in
! the source directory.) Because the core code has changed so
significantly, there are certain liberties that earlier versions of
Apache (and the NCSA daemon) took that recent Apache versions are
pickier about - please check the <a
--- 7,23 ----
<h2>API Changes</h2>
! <p>Some non-compatible changes were made to the Apache API in order to
! deal with HTTP/1.1 compatibility. It is possible that some modules
! will no longer work (specifically, those that process input using the
! POST or PUT methods). If you encounter a module that does not work,
! please contact the author. A <a
! href="client_block_api.html">programmer's note</a> on the subject is
! available.</p>
! <h2>New Features with Apache 1.2</h2>
<p>New features with this release, as extensions of the Apache
! functionality Because the core code has changed so
significantly, there are certain liberties that earlier versions of
Apache (and the NCSA daemon) took that recent Apache versions are
pickier about - please check the <a
***************
*** 27,202 ****
<p>In addition to a number of bug fixes and internal performance
enhancements, <a href="../../dist/">Apache
! 1.1</a> has the following specific new user features:</p>
<ul>
! <li><b><a href="keepalive.html">Support for Keep-Alive Persistent
! Connections</a></b><br> Apache now has (optional) support for persistent
! connections, as defined by the HTTP/1.1 draft. This protocol,
! supported by a number of current HTTP servers and browsers (including
! Netscape Navigator 2.0) has been shown to increase speed of document
! transfer by up to 50% in certain cases.
!
! <li><b><a href="host.html">New non-IP Intensive VirtualHost
! Support</a></b><br>
! Apache's support for virtual hosts has been enhanced to be able to
! use information sent by some new Web browsers to determine the server
! being accessed, without requiring an additional IP address for each
! host.
!
! <li><b><a href="bind.html">Listen to Multiple Addresses and
! Ports</a></b><br>
! Using the new <code>Listen</code> directive, Apache can listen to more
! than one port and IP address, using the same configuration set.
!
! <li><b><a href="mod_status.html">Status
! Module</a></b><br>
! Apache now contains a module that gives the webmaster accurate,
! up-to-date information about the server's status and its resource
! consumption. It also gives the current state of each server process
! including the current URL being processed. For an example, check out
! <A HREF="http://www.apache.org/status">the status of the
! www.apache.org server</A>.
!
! <li><b><a href="mod_info.html">Server Information Module</a></b></br>
! This module gives a plethora of information about the other modules
! installed, their directives, and their configurations. It is
! extremely helpful in debugging configuration problems. For an
! example, check out <A
! HREF="http://www.apache.org/serv-info">information about the
! www.apache.org server</A>.
!
! <li><b><a href="mod_proxy.html">Experimental Caching Proxy Server</a></b><br>
! Apache can now act as
! an HTTP proxy server, allowing clients behind firewalls to use the
! server to access the outside world. In addition, it can cache
! documents it proxies, speeding up access to frequently requested
! documents.
!
! <li><b><a href="location.html">URL-based Access Protection</a></b><br>
! In addition to access checking and authorization by filename (with
! <code><a href="../core.html#directory"><Directory></a></code>),
! the new <code><Location></code> directive allows protection by
! URL.
!
! <li><b><a href="mod_actions.html">Filetype-based Script "Actions"</a></b><br>
! You can now run CGI scripts whenever a file of a certain type is
! requested. This makes it much easier to execute scripts that process
! files. In addition, you can use the new <a
! href="mod_actions.html#script">Script</a> directive to enable scripts
! for files called with HTTP methods Apache does not natively support.
!
! <li><b><a href="handler.html">New "Handler" Directives</a></b><br>
! The new <code>AddHandler</code> and <code>SetHandler</code> directive
! allows "handlers" to be defined for filename extensions or
! directories. These handlers, which can either be built into Apache or
! added with the <a href="mod_actions.html">Action</a> directive, extend
! Apache's range of usability, and almost entirely remove the "magic"
! media types.
! <li><b><a href="mod_env.html">Customizable CGI Environment
Variables</a></b><br>
! New <code>PassEnv</code> and <code>SetEnv</code> directives allow you to
! modify the environment variables passed to CGI scripts.
!
! <li><b><a href="mod_cern_meta.html">CERN Metafile Support</a></b><br>
! Now emulates the CERN httpd's support for metafiles containing additional
! HTTP headers to be supplied with a document.
!
! <li><b><a href="mod_imap.html">Improved Imagemap Support</a></b><br>
! The internal imagemap handling code has been rewritten and
! reorganized, adding new handling of default, base and relative URLs,
! and support for creating non-graphical menus for use with clients that
! do not support imagemaps.
!
! <li><b><a href="mod_userdir.html">Improved UserDir Directive</a></b><br>
! Now supports the ability to point user's files (as specificed by URLs
! beginning with the "<code>~</code>" character) at directories other
! than those specified by the Unix password file.
!
! <li><b>Minimal DNS Now Runtime Option</b><br>
! New <code>HostnameLookups</code>
! server configuration directive can be used to turn <code>On</code> or
! <code>Off</code> DNS lookups. This supercedes the -DMINIMAL_DNS
! compile-time configuration option. This option can be set per-directory.
!
! <li><b>IdentityCheck Now Per-Directory Option</b><br>
! The <code>IdentityCheck</code> directive, which controls the use of
! ident to check the remote user name, can now be set per directory. The
! ident support is also RFC 1413-compliant.
!
! <li><b>Redirect Now Usable in <code>.htaccess</code> Files</b><br>
! The <a href="../mod_alias.html#redirect"><code>Redirect</code></a>
! directive can now be used in <code>.htaccess</code> files when the
! <code>FileInfo</code> directive has been set on. This allows users to
! redirect parts of their directories without requiring CGI scripts
!
! <li><b>ErrorDocument Now Usable in <code>.htaccess</code> Files</b><br>
! The <a href="../custom-error.html"><code>ErrorDocument</code></a>
! directive can now be used in <code>.htaccess</code> files when the
! <code>FileInfo</code> directive has been set on. This allows users to
! have different error messages for different sections of a site.
!
! <li><b><code>ForceType</code> Directive</b><br>
! This new directive, in <code><Directory></code> sections or
! .htaccess files, allows you to override the filename extensions and
! force a single content type. (e.g. <code>ForceType
! application/octet-stream</code>)
!
! <li><b>File Owner Available to Included CGI Scripts</b><br>
! Server-side includes that call CGI scripts will now set a
! <code>USER_NAME</code> environment variable that contains the owner of
! the file which included it.
!
! <li><b>Improved Icons</b><br>
! Thanks to <a href="mailto:kevinh@eit.com">Kevin
! Hughes</a>, Apache's nifty color GIF icons for directory listings have
! been updated. In addition, the <a
! href="../../images/apache_pb.gif">Powered by Apache</a>
! (<code>apache_pb.gif</code>) logo has been included.
</ul>
-
- <hr>
-
- <h3>New Authentication Modules</h3>
-
- <p><strong>Note:</strong> These modules are not
- compiled into the server by default, as they require special support
- on the host system. They must be enabled specifically in the
- <code>Configuration</code> file.</p>
-
- <ul>
-
- <li><b><a href="mod_auth_anon.html">Anonymous HTTP Logins</a></b><br>
- New options allow you to allow, using Basic HTTP Authentication,
- anonymous logins, like those of FTP. This allows you to collect email
- addresses of people accessing your site.
-
- <li><b><a href="mod_digest.html">Support for Digest
- Authentication</a></b> [Documentation to be written]<br>
- Apache now supports digest authentication using RSA MD5
- encryption. When used with a supporting web browser, this provides a
- more secure alternative to Basic authentication.
-
- <li><strong><a href="mod_auth_db.html">Support for Unix DB
- Authentication</a></strong> - <code>mod_auth_db.c</code><br> In
- addition to <a href="../mod_auth_dbm.html">DBM</a> support, Apache now
- contains optional support for Berkeley DB databases.
-
- <li><strong><a href="mod_auth_msql.html">mSQL Database
- Authentication</a></strong> - <code>mod_auth_msql.html</code> <BR>
- Support for the use of mSQL databases for user authentication via HTTP
- is now supported.
-
- </ul>
-
- <hr>
-
- <h3>OS/2 Support</h3>
-
- <p>Apache now includes support for OS/2, thanks to <a href="http://www.slink.com/ApacheOS2/">Softlink Services.</a></p>
<hr>
--- 27,156 ----
<p>In addition to a number of bug fixes and internal performance
enhancements, <a href="../../dist/">Apache
! 1.2</a> has the following specific new user features:</p>
<ul>
! <li><b><a name="http11.html">HTTP/1.1 Compliance</a></b><br>
! Apache (except for the optional proxy) is fully compliant with
! the new HTTP/1.1 standard, as ratified
! by the <a href="http://www.ics.uci.edu/pub/ietf/http/">IETF HTTP
! working group</a>. HTTP/1.1 provides a much-improved protocol, and
! should allow for greater performance and efficiency when transfering
! files. Apache does, however, still work great with HTTP/1.0 browsers.
!
! <li><b><a href="xssi.html">eXtended Server Side Includes
! (XSSI)</a></b><br>
! A new set of server-side include
! directives allows the user to better create WWW pages. This includes
! number of powerful new features, such as the ability to set variables
! and use conditional HTML.
!
! <li><b><a name="files.html">File-based and Regex-enabled Directive
! Sections</a></b><br>
! The new <code><Files></code> section allows directives to be
! enabled based on full filename, not just directory and URL. In
! addition, <code><Files></code> sections can appear in
! <code>.htaccess</code> files. <code><Files></code>, along with
! <code><Directory></code> and <code><Location></code>, can
! also now be based on regular expressions, not just simple prefix
! matching.
! <li><b><a name="mod_browser.html">Browser-based Environment
Variables</a></b><br>
! Environment variables can now be set based on the
! <code>User-Agent</code> string of the browser. Combined with <a
! href="xssi.html">XSSI</a>, this allows you to write browser-based
! conditional HTML documents.
!
! <li><b><a name="sucgi.html">SetUID CGI Execution</a></b>
! Apache now
! supports the execution of CGI scripts as users other
! than the server user. A number of security checks are built in
! to try and make this as safe as possible.
!
! <li><b><a name="mod_rewrite.html">URL Rewriting Module</a></b><br>
! The optional <code>mod_rewrite</code> module is now included. This
! module can provide powerful URL mapping, using regular
! expressions. There's nothing this module can't do!
!
! <li><b><a href="mod_fastcgi.html">Optional FastCGI Module Included</a></b><br>
! FastCGI is a high-performance alternative to CGI. FastCGI gets its speed by having the Web server keep the
! application processes running between requests. So, unlike CGI, you do not have the overhead of starting up
! a new process and doing application initialization (e.g. connecting to a database) each time somebody requests
! a document. The processes start up with the Web server and keep on running.
!
! <li><b><a name="mod_log_config.html">Enhanced, Configurable
! Logging</a></b><br>
! The optional <code>mod_log_config</code> included with earlier
! versions of Apache is now standard, and has been enhanced to allow
! logging of much more detail about the transaction, and can be used to
! open more than one log at once (each of which can have a different log
! format).
!
! <li><b><a href="mod_usertrack.html">User Tracking (Cookies)
! Revisions</a></b><br>
! The <code>mod_cookies</code> included with previous versions of Apache
! has been renamed <code>mod_usertrack</code>, to more accurately
! reflect its function (some people inadvertantely thought it enabled
! cookie support in Apache, which is not true - Apache supports the use
! of cookies directly). It is also now possible to disable the
! generation of cookies, even when
! the cookie module is compiled in. Also, an expiry time can be set
! of the cookies.
!
! <li><b><a name="multi_ip.html">Multiple IPs in <VirtualHost></a></b><br>
! The <VirtualHost> directive can now take more than one IP
! address or hostname. This lets a single vhost handles requests
! for multiple IPs or hostnames.
!
! <li><b><a name="cgi_debug.html">CGI Debugging Environment</a></b><br>
! <code>ScriptLog</code> allows you to now set up a log that records
! all input and output to failed CGI scripts. This includes environment
! variables, input headers, POST data, output, and more. This makes CGI
! scripts much easier to debug.
!
! <li><b><a name="rlimit.html">Resource Limits for CGI Scripts</a></b><br>
! New directives allow the limiting of resources used by CGI scripts
! (e.g. max CPU time). This is helpful in preventing 'runaway' CGI
! processes.
!
! <li><b><a name="graceful.html">Graceful Restarts</a></b><br>
! Apache can re-read the config files and re-open log files without
! terminating transactions in progress.
!
! <li><b><a name="Configure.html">Simplified Compliation</a></b><br>
! The process of configuring Apache for compilation has been
! simplified.
!
! <li><b><a name="help.html">Command-line Help</a></b><br>
! The <code>-h</code> command-line option now lists all the available
! directives.
!
! <li><b><a name="mod_pics_simple.html">Optional PICS module</a></b><br>
! An optional module is included which can provide PICS labels.
!
! <li><b><a name="ifmod.html">Conditional Config Directives</a></b><br>
! A new <code><IfModule></code> section allows directives to be
! enabled only if a given module is loaded into the server.
!
! <li><b><a name="ncsa_auth.html">Authorization Directives Now Use
! NCSA-style Syntax</a></b><br>
! The AuthUserFile, AuthGroupFile and AuthDigestFile commands now have a syntax
! compatible with the NCSA server.
!
! <li><b><a name="mod_proxy.html">Optional proxy module</a></b><br>
! An improved FTP, HTTP, and CONNECT mode SSL proxy is included with
! Apache 1.2. Some of the changes visible to users:
! <dl><dl>
! <dt>- Improved FTP proxy supporting PASV mode
! <dt>- NoProxy directive for excluding sites to proxy
! <dt>- CONNECT mode ports are configurable from a list
! <dt>- NoCache * directive for disabling proxy caching
! <dt>- Numerous bug fixes
! </dl></dl>
</ul>
<hr>
1.2 +31 -0 apache/docs/known_bugs.html
Index: known_bugs.html
===================================================================
RCS file: /export/home/cvs/apache/docs/known_bugs.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** known_bugs.html 1996/11/17 20:22:44 1.1
--- known_bugs.html 1996/11/17 20:34:12 1.2
***************
*** 12,17 ****
--- 12,48 ----
<P>See Also: <A HREF="compat_notes.html">Compatibility notes</A></P>
<HR>
+ <H2>Version 1.1.1</H2>
+
+ <OL>
+
+ <LI>Hostnames such as "123.hotwired.com" are valid, yet
+ find_allowdeny does not properly handle them. This should be put on
+ Known Bugs. Be careful when fixing this because just removing the
+ isalpha() check creates a security hole, consider the DNS map
+ "1.1.1.1.in-addr.arpa IN PTR 2.2.2." if the user has a config line
+ "allow from 2.2.2" it will allow 1.1.1.1 in (unless -DMAXIMUM_DNS).
+ -- which is bad because it breaks people who understand double reverse
+ lookup and are trying to avoid it by using only ip addresses on
+ allow/deny statements. - reported by Dean Gaudet
+
+ </OL>
+
+
+ <H2>Version 1.1.0</H2>
+
+ <OL>
+ <LI>mod_auth_msql misbehaviors. Grab a newer version from
+ <A HREF="../dist/contrib/modules/">the modules distribution
+ directory</A>. -fixed in 1.1
+
+ <LI>Hanging on Netscape 2.0-3.0b4 on MSWindows (3.1 and 95) -
+ we investigated pretty seriously, and as best we can tell
+ this is a Netscape bug, and was fixed in 3.0b5. Please read our
+ <A HREF="windoz_keepalive.html">lab report</A>.
+
+ </OL>
+
<H2>Version 1.1b2 (beta)</h2>
<OL>
<LI>SunOS has trouble compiling mod_status.c . It'll be fixed
1.2 +3 -3 apache/docs/mod_actions.html
Index: mod_actions.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_actions.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_actions.html 1996/11/17 20:27:03 1.1
--- mod_actions.html 1996/11/17 20:34:12 1.2
***************
*** 5,11 ****
</HEAD>
<BODY>
! <IMG SRC="../../images/apache_sub.gif" ALT="">
<H1>Apache module mod_actions</h1>
This module is contained in the <code>mod_actions.c</code> file, and
--- 5,11 ----
</HEAD>
<BODY>
! <IMG SRC="../images/apache_sub.gif" ALT="">
<H1>Apache module mod_actions</h1>
This module is contained in the <code>mod_actions.c</code> file, and
***************
*** 68,75 ****
<p><hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 68,75 ----
<p><hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +3 -3 apache/docs/mod_alias.html
Index: mod_alias.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_alias.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_alias.html 1996/11/17 20:22:46 1.1
--- mod_alias.html 1996/11/17 20:34:13 1.2
***************
*** 36,49 ****
mapped to local files beginning with <em>directory-filename</em>.
Example:
<blockquote><code>Alias /image /ftp/pub/image</code></blockquote>
! A request for http://myserver/images/foo.gif would cause the server to
! return the file /ftp/pub/images/foo.gif.<p>
See also <A HREF="#scriptalias">ScriptAlias</A>.<p><hr>
<A name="redirect"><h2>Redirect</h2></A>
<!--%plaintext <?INDEX {\tt Redirect} directive> -->
<strong>Syntax:</strong> Redirect <em>url-path url</em><br>
! <Strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_alias<p>
--- 36,49 ----
mapped to local files beginning with <em>directory-filename</em>.
Example:
<blockquote><code>Alias /image /ftp/pub/image</code></blockquote>
! A request for http://myserver/image/foo.gif would cause the server to
! return the file /ftp/pub/image/foo.gif.<p>
See also <A HREF="#scriptalias">ScriptAlias</A>.<p><hr>
<A name="redirect"><h2>Redirect</h2></A>
<!--%plaintext <?INDEX {\tt Redirect} directive> -->
<strong>Syntax:</strong> Redirect <em>url-path url</em><br>
! <Strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_alias<p>
1.2 +1 -1 apache/docs/mod_auth_dbm.html
Index: mod_auth_dbm.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_auth_dbm.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_auth_dbm.html 1996/11/17 20:22:49 1.1
--- mod_auth_dbm.html 1996/11/17 20:34:13 1.2
***************
*** 12,18 ****
This module is contained in the <code>mod_auth_dbm.c</code> file, and
is not compiled in by default. It provides for user authentication using
! DBM files. See the <A HREF="auth_dbm.html">DBM</A> user documentation.
<!--%hypertext -->
<menu>
--- 12,18 ----
This module is contained in the <code>mod_auth_dbm.c</code> file, and
is not compiled in by default. It provides for user authentication using
! DBM files. See the <A HREF="auth_dbm.html">DBM user documentation</a>.
<!--%hypertext -->
<menu>
1.2 +3 -3 apache/docs/mod_cern_meta.html
Index: mod_cern_meta.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_cern_meta.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_cern_meta.html 1996/11/17 20:27:05 1.1
--- mod_cern_meta.html 1996/11/17 20:34:14 1.2
***************
*** 5,11 ****
</HEAD>
<BODY>
! <IMG SRC="../../images/apache_sub.gif" ALT="">
<H1>Apache module mod_cern_meta</h1>
This module is contained in the <code>mod_cern_meta.c</code> file, and
--- 5,11 ----
</HEAD>
<BODY>
! <IMG SRC="../images/apache_sub.gif" ALT="">
<H1>Apache module mod_cern_meta</h1>
This module is contained in the <code>mod_cern_meta.c</code> file, and
***************
*** 64,71 ****
<p><hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 64,71 ----
<p><hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +3 -3 apache/docs/mod_env.html
Index: mod_env.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_env.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_env.html 1996/11/17 20:27:06 1.1
--- mod_env.html 1996/11/17 20:34:14 1.2
***************
*** 5,11 ****
</HEAD>
<BODY>
! <IMG SRC="../../images/apache_sub.gif" ALT="">
<H1>Apache module mod_env</h1>
This module is contained in the <code>mod_env.c</code> file, and
--- 5,11 ----
</HEAD>
<BODY>
! <IMG SRC="../images/apache_sub.gif" ALT="">
<H1>Apache module mod_env</h1>
This module is contained in the <code>mod_env.c</code> file, and
***************
*** 55,62 ****
<p><hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 55,62 ----
<p><hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +4 -4 apache/docs/mod_info.html
Index: mod_info.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_info.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_info.html 1996/11/17 20:27:07 1.1
--- mod_info.html 1996/11/17 20:34:15 1.2
***************
*** 5,11 ****
</head>
<body>
! <IMG SRC="../../images/apache_sub.gif" ALT="">
<h1>Module mod_info</h1>
This module is contained in the <code>mod_info.c</code> file. It
--- 5,11 ----
</head>
<body>
! <IMG SRC="../images/apache_sub.gif" ALT="">
<h1>Module mod_info</h1>
This module is contained in the <code>mod_info.c</code> file. It
***************
*** 23,29 ****
To configure it, add the following to your <code>access.conf</code> file.
<PRE>
! <Location /info>
SetHandler server-info
</Location>
</PRE>
--- 23,29 ----
To configure it, add the following to your <code>access.conf</code> file.
<PRE>
! <Location /server-info>
SetHandler server-info
</Location>
</PRE>
***************
*** 35,42 ****
<!--%hypertext -->
<hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 35,42 ----
<!--%hypertext -->
<hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +71 -0 apache/docs/mod_mime.html
Index: mod_mime.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_mime.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_mime.html 1996/11/17 20:22:55 1.1
--- mod_mime.html 1996/11/17 20:34:15 1.2
***************
*** 35,42 ****
--- 35,45 ----
<h2> Directives</h2>
<ul>
<li><A HREF="#addencoding">AddEncoding</A>
+ <li><A HREF="#addhandler">AddHandler</A>
<li><A HREF="#addlanguage">AddLanguage</A>
<li><A HREF="#addtype">AddType</A>
+ <li><A HREF="#forcetype">ForceType</A>
+ <li><A HREF="#sethandler">SetHandler</A>
<li><A HREF="#typesconfig">TypesConfig</A>
</ul>
<hr>
***************
*** 62,67 ****
--- 65,90 ----
This will cause files ending in .gz to be marked as encoded using the x-gzip
encoding, and .Z files to be marked as encoded with x-compress.<p><hr>
+ <h2><a name="addhandler">AddHandler</a></h2>
+
+ <strong>Syntax:</strong> <AddHandler <em>handler-name extention</em>><br>
+ <strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
+ <strong>Status:</strong> Base<br>
+ <strong>Module:</strong> mod_mime
+
+ <p>AddHandler maps the filename extension <em>extension</em> to the
+ <a href="handler.html">handler</a>
+ <em>handler-name</em>. For example, to activate CGI scripts
+ with the file extension "<code>.cgi</code>", you might use:
+ <pre>
+ AddHandler cgi-script cgi
+ </pre>
+
+ <p>Once that has been put into your srm.conf or httpd.conf file, any
+ file ending with "<code>.cgi</code>" will be treated as a CGI
+ program.</p>
+
+
<A name="addlanguage"><h2>AddLanguage</h2></A>
<!--%plaintext <?INDEX {\tt AddLanguage} directive> -->
<strong>Syntax:</strong> AddLanguage <em>mime-lang extension extension...</em><br>
***************
*** 105,110 ****
--- 128,181 ----
rather than changing the <A HREF="#typesconfig">TypesConfig</A> file.<p>
Note that, unlike the NCSA httpd, this directive cannot be used to set the
type of particular files.<p><hr>
+
+ <h2><a name="sethandler">ForceType</a></h2>
+
+ <strong>Syntax:</strong> <ForceType <em>media type</em>><br>
+ <strong>Context:</strong> directory, .htaccess<br>
+ <strong>Status:</strong> Base<br>
+ <strong>Module:</strong> mod_mime
+
+ <p>When placed into an <code>.htaccess</code> file or a
+ <code><Directory></code> or <code><Location</code> section,
+ this directive forces all matching files to be served
+ as the content type given by <em>media type</em>. For example, if you
+ had a directory full of GIF files, but did not want to label them all with
+ ".gif", you might want to use:
+ <pre>
+ ForceType image/gif
+ </pre>
+ <p>Note that this will override any filename extensions that might
+ media type.</p>
+
+ <h2><a name="sethandler">SetHandler</a></h2>
+
+ <strong>Syntax:</strong> <SetHandler <em>handler-name</em>><br>
+ <strong>Context:</strong> directory, .htaccess<br>
+ <strong>Status:</strong> Base<br>
+ <strong>Module:</strong> mod_mime
+
+ <p>When placed into an <code>.htaccess</code> file or a
+ <code><Directory></code> or <code><Location</code> section,
+ this directive forces all matching files to be parsed through the
+ <a href="handler.html">handler</a>
+ given by <em>handler-name</em>. For example, if you had a
+ directory you wanted to be parsed entirely as imagemap rule files,
+ regardless of extension, you might put the following into an
+ <code>.htaccess</code> file in that directory:
+ <pre>
+ SetHandler imap-file
+ </pre>
+
+ <p>Another example: if you wanted to have the server display a status
+ report whenever a URL of <code>http://servername/status</code> was
+ called, you might put the following into access.conf:
+ <pre>
+ <Location /status>
+ SetHandler server-status
+ </Location>
+ </pre>
+
<A name="typesconfig"><h2>TypesConfig</h2></A>
<!--%plaintext <?INDEX {\tt TypesConfig} directive> -->
1.2 +15 -1 apache/docs/mod_negotiation.html
Index: mod_negotiation.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_negotiation.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_negotiation.html 1996/11/17 20:22:55 1.1
--- mod_negotiation.html 1996/11/17 20:34:16 1.2
***************
*** 86,103 ****
<!--%hypertext -->
<h2>Directives</h2>
<ul>
<li><A HREF="#languagepriority">LanguagePriority</A>
</ul>
<hr>
<!--/%hypertext -->
<A name="languagepriority"><h2>LanguagePriority</h2></A>
<!--%plaintext <?INDEX {\tt LanguagePriority} directive> -->
<strong>Syntax:</strong> LanguagePriority <em>mime-lang mime-lang...</em><br>
<Strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
<Strong>Override:</strong> FileInfo<br>
<strong>Status:</strong> Base<br>
! <strong>Module:</strong> mod_mime<p>
The LanguagePriority sets the precedence of language variants for the case
where the client does not express a preference, when handling a
--- 86,117 ----
<!--%hypertext -->
<h2>Directives</h2>
<ul>
+ <li><A href="#cachenegotiateddocs">CacheNegotiatedDocs</a>
<li><A HREF="#languagepriority">LanguagePriority</A>
</ul>
<hr>
<!--/%hypertext -->
+ <A name="cachenegotiateddocs"><h2>CacheNegotiatedDocs</h2></A>
+ <strong>Syntax:</strong> CacheNegotiatedDocs<br>
+ <Strong>Context:</strong> server config<br>
+ <strong>Status:</strong> Base<br>
+ <strong>Module:</strong> mod_negotiation<p>
+
+ <p>If set, this directive allows content-negotiated documents to be cached
+ by
+ proxy servers. This could mean that clients behind those proxys could
+ retrieve versions of the documents that are not the best match for
+ their abilities, but it will make caching more efficient.</p>
+
+ <!--%hypertext -->
<A name="languagepriority"><h2>LanguagePriority</h2></A>
<!--%plaintext <?INDEX {\tt LanguagePriority} directive> -->
<strong>Syntax:</strong> LanguagePriority <em>mime-lang mime-lang...</em><br>
<Strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
<Strong>Override:</strong> FileInfo<br>
<strong>Status:</strong> Base<br>
! <strong>Module:</strong> mod_negotiation<p>
The LanguagePriority sets the precedence of language variants for the case
where the client does not express a preference, when handling a
1.2 +17 -17 apache/docs/mod_proxy.html
Index: mod_proxy.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_proxy.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_proxy.html 1996/11/17 20:27:07 1.1
--- mod_proxy.html 1996/11/17 20:34:16 1.2
***************
*** 5,16 ****
</HEAD>
<BODY>
! <IMG SRC="../../images/apache_sub.gif" ALT="">
<H1>Apache module mod_proxy</h1>
! This module is contained in the <code>mod_proxy.c</code> file, and is
! not compiled in by default. It provides for a caching <A
! HREF="http://www.w3.org/pub/WWW/Proxies/">proxy server</A>.
<h3>Note:</h3>
<p>This module is experimental. Use at your own risk.</p>
--- 5,15 ----
</HEAD>
<BODY>
! <IMG SRC="../images/apache_sub.gif" ALT="">
<H1>Apache module mod_proxy</h1>
! This module is contained in the <code>mod_proxy.c</code> file, and
! is not compiled in by default. It provides for a caching proxy server.
<h3>Note:</h3>
<p>This module is experimental. Use at your own risk.</p>
***************
*** 58,75 ****
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_proxy<p>
! This defines remote proxies to this proxy. <match> is either the
! name of a URL-scheme that the remote server supports, or a partial URL
! for which the remote server should be used, or '$' to indicate the
! server should be contacted for all requests. <remote-server> is
! a partial URL for the remote server. Syntax:
!
<pre>
<remote-server> = <protocol>://<hostname>[:port]
</pre>
!
! <protocol> is the protocol that should be used to communicate
! with the remote server; only "http" is supported by this module.
Example:
<pre>
--- 57,75 ----
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_proxy<p>
! This defines remote proxies to this proxy. <match> is either the name
! of a URL-scheme that the remote server supports, or a partial URL for
! which
! the remote server should be used, or '$' to indicate the server should
! be
! contacted for all requests. <remote-server> is a partial URL for the
! remote server. Syntax:
<pre>
<remote-server> = <protocol>://<hostname>[:port]
</pre>
! <protocol> is the protocol that should be used to communicate with the
! remote
! server; only "http" is supported by this module.
Example:
<pre>
***************
*** 86,93 ****
This directive allows remote servers to be mapped into the space of the local
server; the local server does not act as a proxy in the conventional sense,
! but appears to be a mirror of the remote server. <path> is the name of
! a local virtual path; <url> is a partial URL for the remote server.
Suppose the local server has address http://wibble.org; then
<pre>
--- 86,93 ----
This directive allows remote servers to be mapped into the space of the local
server; the local server does not act as a proxy in the conventional sense,
! but appears to be a mirror of the remote server. <path> is the name of
! a local virtual path; <url> is a partial URL for the remote server.
Suppose the local server has address http://wibble.org; then
<pre>
***************
*** 184,191 ****
<p><hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 184,191 ----
<p><hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +7 -7 apache/docs/mod_status.html
Index: mod_status.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_status.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_status.html 1996/11/17 20:27:08 1.1
--- mod_status.html 1996/11/17 20:34:17 1.2
***************
*** 2,8 ****
<title>Apache Status Module</title>
</head><body>
! <img src="../../images/apache_sub.gif" alt="">
<h1>Apache Status Module</h1>
<hr>
--- 2,8 ----
<title>Apache Status Module</title>
</head><body>
! <img src="../images/apache_sub.gif" alt="">
<h1>Apache Status Module</h1>
<hr>
***************
*** 41,47 ****
To enable status reports only for browsers from the foo.com
domain add this code to your <code>access.conf</code> configuration file
<pre>
! <Location /status>
SetHandler server-status
<Limit GET POST>
--- 41,47 ----
To enable status reports only for browsers from the foo.com
domain add this code to your <code>access.conf</code> configuration file
<pre>
! <Location /server-status>
SetHandler server-status
<Limit GET POST>
***************
*** 53,67 ****
</pre>
<p>
You can now access server statistics by using a Web browser to access the
! page <code>http://your.server.name/status/</code>
<h3>Automatic Updates</h3>
You can get the status page to update itself automatically if you have
a browser that supports "refresh". Access the page
! <code>http://your.server.name/status/?refresh=N</code> to refresh the page
every N seconds.
<h3>Machine Readable Status File</h3>
A machine-readable version of the status file is available by accessing the
! page <code>http://your.server.name/status/?auto</code>. This is useful
when automatically run, see the Perl program in the <code>/support</code>
directory of Apache, <code>log_server_status</code>.
--- 53,67 ----
</pre>
<p>
You can now access server statistics by using a Web browser to access the
! page <code>http://your.server.name/server-status</code>
<h3>Automatic Updates</h3>
You can get the status page to update itself automatically if you have
a browser that supports "refresh". Access the page
! <code>http://your.server.name/server-status?refresh=N</code> to refresh the page
every N seconds.
<h3>Machine Readable Status File</h3>
A machine-readable version of the status file is available by accessing the
! page <code>http://your.server.name/server-status?auto</code>. This is useful
when automatically run, see the Perl program in the <code>/support</code>
directory of Apache, <code>log_server_status</code>.
***************
*** 84,91 ****
<hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="../"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 84,91 ----
<hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="../"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.3 +3 -3 apache/docs/mod_userdir.html
Index: mod_userdir.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_userdir.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_userdir.html 1996/11/17 20:27:08 1.2
--- mod_userdir.html 1996/11/17 20:34:17 1.3
***************
*** 6,12 ****
</HEAD>
<BODY>
! <IMG SRC="../../images/apache_sub.gif" ALT="">
<!--/%hypertext -->
<H1>Module mod_userdir</h1>
--- 6,12 ----
</HEAD>
<BODY>
! <IMG SRC="../images/apache_sub.gif" ALT="">
<!--/%hypertext -->
<H1>Module mod_userdir</h1>
***************
*** 46,53 ****
</pre>
<!--%hypertext -->
<hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 46,53 ----
</pre>
<!--%hypertext -->
<hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +20 -0 apache/docs/modules.html
Index: modules.html
===================================================================
RCS file: /export/home/cvs/apache/docs/modules.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** modules.html 1996/11/17 20:22:56 1.1
--- modules.html 1996/11/17 20:34:18 1.2
***************
*** 13,38 ****
--- 13,54 ----
<dd>Core Apache features.
<dt><A HREF="mod_access.html">mod_access</A>
<dd>Host based access control.
+ <dt><A HREF="mod_actions.html">mod_actions</A>
+ <dd>Filetype/method-based script execution
<dt><A HREF="mod_alias.html">mod_alias</A>
<dd>Aliase and redirects.
<dt><A HREF="mod_asis.html">mod_asis</A>
<dd>The .asis file handler.
<dt><A HREF="mod_auth.html">mod_auth</A>
<dd>User authentication using text files.
+ <dt><A HREF="mod_auth_anon.html">mod_auth_anon</A>
+ <dd>Anonymous user authentication, FTP-style.
+ <dt><A HREF="mod_auth_db.html">mod_auth_db</A>
+ <dd>User authentication using Berkeley DB files.
<dt><A HREF="mod_auth_dbm.html">mod_auth_dbm</A>
<dd>User authentication using DBM files.
+ <dt><A HREF="mod_auth_msql.html">mod_auth_msql</A>
+ <dd>User authentication using mSQL files.
+ <dt><A HREF="mod_cern_meta.html">mod_cern_meta</a>
+ <dd>Support for HTTP header metafiles.
<dt><A HREF="mod_cgi.html">mod_cgi</A>
<dd>Invoking CGI scripts.
<dt><A HREF="mod_cookies.html">mod_cookies</A>
<dd>Support for Netscape-like cookies.
+ <dt><A HREF="mod_digest.html">mod_digest</A>
+ <dd>MD5 authentication
<dt><A HREF="mod_dir.html">mod_dir</A>
<dd>Automatic directory listings.
+ <dt><A HREF="mod_env.html">mod_env</A>
+ <dd>Passing of environments to CGI scripts
<dt><A HREF="mod_dld.html">mod_dld</A>
<dd>Start-time linking with the GNU libdld.
<dt><A HREF="mod_imap.html">mod_imap</A>
<dd>The imagemap file handler.
<dt><A HREF="mod_include.html">mod_include</A>
<dd>Server-parsed documents.
+ <dt><A HREF="mod_info.html">mod_info</a>
+ <dd>Server configuration information
<dt><A HREF="mod_log_agent.html">mod_log_agent</A>
<dd>Logging of User Agents.
<dt><A HREF="mod_log_common.html">mod_log_common</A>
***************
*** 45,50 ****
--- 61,70 ----
<dd>Determining document types.
<dt><A HREF="mod_negotiation.html">mod_negotiation</A>
<dd>Content negotation.
+ <dt><A HREF="mod_proxy.html">mod_proxy</A>
+ <dd>Caching proxy abilities
+ <dt><A HREF="mod_status.html">mod_status</a>
+ <dd>Server status display
<dt><A HREF="mod_userdir.html">mod_userdir</A>
<dd>User home directories.
</dl>
1.2 +8 -0 apache/docs/perf-bsd44.html
Index: perf-bsd44.html
===================================================================
RCS file: /export/home/cvs/apache/docs/perf-bsd44.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** perf-bsd44.html 1996/11/17 20:22:58 1.1
--- perf-bsd44.html 1996/11/17 20:34:19 1.2
***************
*** 172,177 ****
--- 172,185 ----
Finally, there's the hard limit of child processes configured in Apache.
+ <p>
+
+ You'll need to change the definition for <b>HARD_SERVER_LIMIT</b> in
+ <i>httpd.h</i> and recompile if you need to run more than the default 150
+ instances of httpd.
+
+ <p>
+
From conf/httpd.conf-dist:
<pre>
1.2 +28 -4 apache/docs/perf.html
Index: perf.html
===================================================================
RCS file: /export/home/cvs/apache/docs/perf.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** perf.html 1996/11/17 20:22:59 1.1
--- perf.html 1996/11/17 20:34:19 1.2
***************
*** 19,25 ****
--- 19,27 ----
<LI><A HREF="#AUX">A/UX (Apple's UNIX)</A>
<LI><A HREF="#BSD">BSD-based (BSDI, FreeBSD, etc)</A>
<LI><A HREF="#DEC">Digital UNIX</A>
+ <LI><A HREF="#HP">Hewlett-Packard</A>
<LI><A HREF="#Linux">Linux</A>
+ <LI><A HREF="#SGI">SGI</A>
<LI><A HREF="#Solaris">Solaris</A>
<LI><A HREF="#SunOS">SunOS 4.x</A>
</UL>
***************
*** 56,61 ****
--- 58,72 ----
<P><HR>
+ <A NAME="HP">
+ <H3>Hewlett-Packard</H3>
+ </A>
+
+ Some documentation on tuning HP machines can be found at <A
+ HREF="http://www.software.hp.com/internet/perf/tuning.html">http://www.software.hp.com/internet/perf/tuning.html</A>.
+
+ <P><HR>
+
<A NAME="Linux">
<H3>Linux</H3>
</A>
***************
*** 66,76 ****
listen() queue overload - certain Linux implementations have a low
value set for the incoming connection queue which can cause problems.
Please see our <a
! href="http://www.qosina.com/apache/linux-tcp.html">Using Apache on
Linux</a> page for more info on how to fix this.
<P><HR>
<A NAME="Solaris">
<H3>Solaris 2.4</H3>
</A>
--- 77,98 ----
listen() queue overload - certain Linux implementations have a low
value set for the incoming connection queue which can cause problems.
Please see our <a
! href="http://www.qosina.com/~awm/apache/linux-tcp.html">Using Apache on
Linux</a> page for more info on how to fix this.
<P><HR>
+ <A NAME="SGI">
+ <H3>SGI</H3>
+
+ <UL>
+ <LI><A HREF="http://www.sgi.com/Products/WebFORCE/TuningGuide.html">
+ WebFORCE Web Server Tuning Guidelines for IRIX 5.3,
+ <http://www.sgi.com/Products/WebFORCE/TuningGuide.html></A>
+ </UL>
+
+ <P><HR>
+
<A NAME="Solaris">
<H3>Solaris 2.4</H3>
</A>
***************
*** 81,90 ****
the following URL for tips on how to expand the capabilities if you
are finding slowdowns and lags are hurting performance.
! <P>
! <A href="http://www.sun.com/cgi-bin/show?sun-on-net/Sun.Internet.Solutions/performance/index.html">
! http://www.sun.com/cgi-bin/show?sun-on-net/Sun.Internet.Solutions/performance/index.html</a>
<P><HR>
--- 103,114 ----
the following URL for tips on how to expand the capabilities if you
are finding slowdowns and lags are hurting performance.
! <UL>
! <LI><A href="http://www.sun.com/cgi-bin/show?sun-on-net/Sun.Internet.Solutions/performance/">
! World Wide Web Server Performance,
! <http://www.sun.com/cgi-bin/show?sun-on-net/Sun.Internet.Solutions/performance/></a>
! </UL>
<P><HR>
1.2 +8 -4 apache/docs/virtual-host.html
Index: virtual-host.html
===================================================================
RCS file: /export/home/cvs/apache/docs/virtual-host.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** virtual-host.html 1996/11/17 20:23:02 1.1
--- virtual-host.html 1996/11/17 20:34:20 1.2
***************
*** 7,12 ****
--- 7,16 ----
<body>
<IMG SRC="../images/apache_sub.gif" ALT="">
<h1>Virtual Host Support</h1>
+
+ <strong>See Also:</strong>
+ <a href="host.html">Non-IP based virtual hosts</a>
+
<h2>What are virtual hosts?</h2>
This is the ability of a single machine to be a web server for multiple
domains. For example, an internet service provider might have a machine
***************
*** 55,62 ****
<ul>
<li>The different virtual hosts need very different httpd configurations, such
as different values for: <A HREF="core.html#servertype">ServerType</A>,
! <A HREF="core.html#userid">UserId</A>,
! <A HREF="core.html#groupid">GroupId</A>,
<A HREF="mod_mime.html#typesconfig">TypesConfig</A> or
<A HREF="core.html#serverroot">ServerRoot</A>.
<li>The machine does not process a very high request rate.
--- 59,66 ----
<ul>
<li>The different virtual hosts need very different httpd configurations, such
as different values for: <A HREF="core.html#servertype">ServerType</A>,
! <A HREF="core.html#user">User</A>,
! <A HREF="core.html#group">Group</A>,
<A HREF="mod_mime.html#typesconfig">TypesConfig</A> or
<A HREF="core.html#serverroot">ServerRoot</A>.
<li>The machine does not process a very high request rate.
***************
*** 113,120 ****
Almost <strong>ANY</strong> configuration directive can be put
in the VirtualHost directive, with the exception of
<A HREF="core.html#servertype">ServerType</A>,
! <A HREF="core.html#userid">UserId</A>,
! <A HREF="core.html#groupid">GroupId</A>,
<A HREF="core.html#startservers">StartServers</A>,
<A HREF="core.html#maxspareservers">MaxSpareServers</A>,
<A HREF="core.html#minspareservers">MinSpareServers</A>,
--- 117,124 ----
Almost <strong>ANY</strong> configuration directive can be put
in the VirtualHost directive, with the exception of
<A HREF="core.html#servertype">ServerType</A>,
! <A HREF="core.html#user">User</A>,
! <A HREF="core.html#group">Group</A>,
<A HREF="core.html#startservers">StartServers</A>,
<A HREF="core.html#maxspareservers">MaxSpareServers</A>,
<A HREF="core.html#minspareservers">MinSpareServers</A>,