randy 96/12/02 10:14:23
Modified: htdocs/manual bind.html content-negotiation.html
custom-error.html handler.html host.html
invoking.html keepalive.html location.html
man-template.html multilogs.html
new_features_1_0.html new_features_1_1.html
new_features_1_2.html process-model.html
suexec.html virtual-host.html
htdocs/manual/mod core.html index.html mod_actions.html
mod_alias.html mod_auth.html mod_auth_anon.html
mod_auth_db.html mod_auth_dbm.html
mod_auth_msql.html mod_browser.html mod_cgi.html
mod_digest.html mod_dir.html mod_env.html
mod_fastcgi.html mod_headers.html mod_imap.html
mod_include.html mod_log_config.html mod_mime.html
mod_negotiation.html mod_proxy.html
mod_rewrite.html mod_usertrack.html
Log:
Spelling corrections
Revision Changes Path
1.4 +1 -1 apache/htdocs/manual/bind.html
Index: bind.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/bind.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** bind.html 1996/11/26 05:36:38 1.3
--- bind.html 1996/12/02 18:13:38 1.4
***************
*** 79,85 ****
and ports. To implement a VirtualHost, the server must first be told
to listen to the address and port to be used. Then a
<VirtualHost> section should be created for a specified address
! and port to set the behaviour of this virtual host. Note that if the
<VirtualHost> is set for an address and port that the server is
not listening to, it cannot be accessed.
--- 79,85 ----
and ports. To implement a VirtualHost, the server must first be told
to listen to the address and port to be used. Then a
<VirtualHost> section should be created for a specified address
! and port to set the behavior of this virtual host. Note that if the
<VirtualHost> is set for an address and port that the server is
not listening to, it cannot be accessed.
1.3 +1 -1 apache/htdocs/manual/content-negotiation.html
Index: content-negotiation.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/content-negotiation.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** content-negotiation.html 1996/11/21 10:47:08 1.2
--- content-negotiation.html 1996/12/02 18:13:39 1.3
***************
*** 108,114 ****
<code>image/gif</code>, <code>text/plain</code>, or
<code>text/html; level=3</code>.
<dt> <code>Content-language:</code>
! <dd> The language of the variant, specified as an internet standard
language code (e.g., <code>en</code> for English,
<code>kr</code> for Korean, etc.).
<dt> <code>Content-encoding:</code>
--- 108,114 ----
<code>image/gif</code>, <code>text/plain</code>, or
<code>text/html; level=3</code>.
<dt> <code>Content-language:</code>
! <dd> The language of the variant, specified as an Internet standard
language code (e.g., <code>en</code> for English,
<code>kr</code> for Korean, etc.).
<dt> <code>Content-encoding:</code>
1.4 +5 -5 apache/htdocs/manual/custom-error.html
Index: custom-error.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/custom-error.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** custom-error.html 1996/11/26 05:36:39 1.3
--- custom-error.html 1996/12/02 18:13:39 1.4
***************
*** 1,6 ****
<HTML>
<HEAD>
! <TITLE>Ccustom error responses</TITLE>
</HEAD>
<BODY>
--- 1,6 ----
<HTML>
<HEAD>
! <TITLE>Custom error responses</TITLE>
</HEAD>
<BODY>
***************
*** 9,15 ****
<DL>
<DT>Purpose
! <DD>Additional functionality. Allows webmasters to configure the response of
Apache to some error or problem.<BR>
<P>Customizable responses can be defined to be activated in the event of a
server detected error or problem.<BR>
--- 9,15 ----
<DL>
<DT>Purpose
! <DD>Additional functionality. Allows web-masters to configure the response
of
Apache to some error or problem.<BR>
<P>Customizable responses can be defined to be activated in the event of a
server detected error or problem.<BR>
***************
*** 82,95 ****
<h2>Custom error responses and redirects</H2>
<DL>
<DT>Purpose
! <DD>Apache's behaviour to redirected URLs has been modified so that
additional
environment variables are available to a script/server-include.<p>
! <DT>Old behaviour
<DD>Standard CGI vars were made available to a script which has been
redirected to. No indication of where the redirection came from was
provided.
<p>
! <DT>New behaviour
<DD>A new batch of environment variables will be initialized for use by a
script which has been redirected to.<BR>
Each new variable will have the prefix <code>REDIRECT_</code>.<BR>
--- 82,95 ----
<h2>Custom error responses and redirects</H2>
<DL>
<DT>Purpose
! <DD>Apache's behavior to redirected URLs has been modified so that
additional
environment variables are available to a script/server-include.<p>
! <DT>Old behavior
<DD>Standard CGI vars were made available to a script which has been
redirected to. No indication of where the redirection came from was
provided.
<p>
! <DT>New behavior
<DD>A new batch of environment variables will be initialized for use by a
script which has been redirected to.<BR>
Each new variable will have the prefix <code>REDIRECT_</code>.<BR>
1.3 +7 -7 apache/htdocs/manual/handler.html
Index: handler.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/handler.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** handler.html 1996/11/21 10:47:09 1.2
--- handler.html 1996/12/02 18:13:40 1.3
***************
*** 14,20 ****
performed when a file is called. Generally, files have implicit
handlers, based on the file type. Normally, all files are simply
served by the server, but certain file typed are "handled"
! seperately. For example, you may use a type of
"application/x-httpd-cgi" to invoke CGI scripts.</p>
<p>Apache 1.1 adds the additional ability to use handlers
--- 14,20 ----
performed when a file is called. Generally, files have implicit
handlers, based on the file type. Normally, all files are simply
served by the server, but certain file typed are "handled"
! separately. For example, you may use a type of
"application/x-httpd-cgi" to invoke CGI scripts.</p>
<p>Apache 1.1 adds the additional ability to use handlers
***************
*** 48,54 ****
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>
--- 48,54 ----
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 negotiation
(<a href="mod_negotiation.html">mod_negotiation</a>)
</ul>
***************
*** 64,70 ****
<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
--- 64,70 ----
<h2><a name="addhandler">AddHandler</a></h2>
! <strong>Syntax:</strong> <AddHandler <em>handler-name
extension</em>><br>
<strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_mime
***************
*** 122,132 ****
<p>If you wish to have your module engage a handler, you need only to
set <code>r->handler</code> to the name of the handler at any time
prior to the <code>invoke_handler</code> stage of the
! request. Handlers are implemented as they were before, albiet using
the handler name instead of a content type. While it is not
! neccessary, the naming convention for handlers is to use a
! dash-seperated word, with no slashes, so as to not invade the media
! type namespace.</p>
<!--#include virtual="footer.html" -->
</BODY>
--- 122,132 ----
<p>If you wish to have your module engage a handler, you need only to
set <code>r->handler</code> to the name of the handler at any time
prior to the <code>invoke_handler</code> stage of the
! request. Handlers are implemented as they were before, albeit using
the handler name instead of a content type. While it is not
! necessary, the naming convention for handlers is to use a
! dash-separated word, with no slashes, so as to not invade the media
! type name-space.</p>
<!--#include virtual="footer.html" -->
</BODY>
1.3 +7 -7 apache/htdocs/manual/host.html
Index: host.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/host.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** host.html 1996/11/21 10:47:10 1.2
--- host.html 1996/12/02 18:13:40 1.3
***************
*** 12,18 ****
<p>The "Virtual Host" refers to the practice of maintaining more than
one server on one machine, as differentiated by their apparent
hostname. For example, it is often desirable for companies sharing a
! web server to have their own domains, with web servers accessable as
<code>www.company1.com</code> and <code>www.company2.com</code>,
without requiring the user to know any extra path information.</p>
--- 12,18 ----
<p>The "Virtual Host" refers to the practice of maintaining more than
one server on one machine, as differentiated by their apparent
hostname. For example, it is often desirable for companies sharing a
! web server to have their own domains, with web servers accessible as
<code>www.company1.com</code> and <code>www.company2.com</code>,
without requiring the user to know any extra path information.</p>
***************
*** 20,26 ****
out of the box, but since the base <code>HTTP</code> (HyperText
Transport Protocol) standard does not allow any method for the server
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>.
--- 20,26 ----
out of the box, but since the base <code>HTTP</code> (HyperText
Transport Protocol) standard does not allow any method for the server
to determine the hostname it is being addressed as, Apache's virtual
! host support has required a separate IP address for each
server. Documentation on using this approach (which still works very
well) is available <a href="virtual-host.html">here</a>.
***************
*** 60,67 ****
server. Optionally, you could simply use that IP address in the
<VirtualHost> entry.</p>
! <p>Additionally, many servers may wish to be accessable by more than
! one name. For example, the Apache server might want to be accessable
as <code>apache.org</code>, or <code>ftp.apache.org</code>, assuming
the IP addresses pointed to the same server. In fact, one might want it
so that all addresses at <code>apache.org</code> were picked up by the
--- 60,67 ----
server. Optionally, you could simply use that IP address in the
<VirtualHost> entry.</p>
! <p>Additionally, many servers may wish to be accessible by more than
! one name. For example, the Apache server might want to be accessible
as <code>apache.org</code>, or <code>ftp.apache.org</code>, assuming
the IP addresses pointed to the same server. In fact, one might want it
so that all addresses at <code>apache.org</code> were picked up by the
***************
*** 73,79 ****
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>
--- 73,79 ----
ServerAlias apache.org *.apache.org
</pre>
! <p>Note that you can use <code>*</code> and <code>?</code> as wild-card
characters.</p>
<h2>Security Considerations</h2>
***************
*** 95,101 ****
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
--- 95,101 ----
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 intra-net 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
***************
*** 104,110 ****
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>
--- 104,110 ----
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 consistently
respected.
<h2>Compatibility with Older Browsers</h2>
1.5 +2 -2 apache/htdocs/manual/invoking.html
Index: invoking.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/invoking.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C3 -r1.4 -r1.5
*** invoking.html 1996/12/01 06:38:11 1.4
--- invoking.html 1996/12/02 18:13:41 1.5
***************
*** 17,23 ****
but this is not recommended.
<h2>Command line options</h2>
! The following options are recognised on the httpd command line:
<dl>
<dt><code>-d</code> <em>serverroot</em>
<dd>Set the initial value for the
--- 17,23 ----
but this is not recommended.
<h2>Command line options</h2>
! The following options are recognized on the httpd command line:
<dl>
<dt><code>-d</code> <em>serverroot</em>
<dd>Set the initial value for the
***************
*** 68,74 ****
the server can provide to clients. The filename may be overridden with
the <A HREF="mod/core.html#resourceconfig">ResourceConfig</A> directive.
! <dt><code>conf/acces.conf</code>
<dd>Contains directives that control access to documents.
The filename may be overridden with the
<A HREF="mod/core.html#accessconfig">AccessConfig</A> directive.
--- 68,74 ----
the server can provide to clients. The filename may be overridden with
the <A HREF="mod/core.html#resourceconfig">ResourceConfig</A> directive.
! <dt><code>conf/access.conf</code>
<dd>Contains directives that control access to documents.
The filename may be overridden with the
<A HREF="mod/core.html#accessconfig">AccessConfig</A> directive.
1.3 +2 -2 apache/htdocs/manual/keepalive.html
Index: keepalive.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/keepalive.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** keepalive.html 1996/11/21 10:47:12 1.2
--- keepalive.html 1996/12/02 18:13:41 1.3
***************
*** 9,15 ****
<h2>What is Keep-Alive?</h2>
! The Keep-Alive extenstion to HTTP, as defined by the
<code>HTTP/1.1</code> draft, allows persistent connections. These
long-lived HTTP sessions allow multiple requests to be send over the
same TCP connection, and in some cases have been shown to result in an
--- 9,15 ----
<h2>What is Keep-Alive?</h2>
! The Keep-Alive extension to HTTP, as defined by the
<code>HTTP/1.1</code> draft, allows persistent connections. These
long-lived HTTP sessions allow multiple requests to be send over the
same TCP connection, and in some cases have been shown to result in an
***************
*** 59,65 ****
length is known beforehand. This means that most CGI scripts,
server-side included files and directory listings will not use
the Keep-Alive protocol. While this should be completely transparent
! to the end user, it is something the webmaster may want to keep in mind.</p>
<!--#include virtual="footer.html" -->
</BODY>
--- 59,65 ----
length is known beforehand. This means that most CGI scripts,
server-side included files and directory listings will not use
the Keep-Alive protocol. While this should be completely transparent
! to the end user, it is something the web-master may want to keep in
mind.</p>
<!--#include virtual="footer.html" -->
</BODY>
1.3 +3 -3 apache/htdocs/manual/location.html
Index: location.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/location.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** location.html 1996/11/21 10:47:13 1.2
--- location.html 1996/12/02 18:13:41 1.3
***************
*** 15,21 ****
<strong>Status:</strong> core<br>
<p>The <Location> directive provides for access control by
! URL. It is comprable to the <a
href="../core.html#directory"><Directory></a> directive, and
should be matched with a </Location> directive. Directives that
apply to the URL given should be listen
--- 15,21 ----
<strong>Status:</strong> core<br>
<p>The <Location> directive provides for access control by
! URL. It is comparable to the <a
href="../core.html#directory"><Directory></a> directive, and
should be matched with a </Location> directive. Directives that
apply to the URL given should be listen
***************
*** 27,34 ****
<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.
--- 27,34 ----
<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
! necessarily have to protect a directory (it can be an individual
! file, or a number of files), and can include wild-cards. In a wild-card
string, `?' matches any single character, and `*' matches any
sequences of characters.
1.3 +1 -1 apache/htdocs/manual/man-template.html
Index: man-template.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/man-template.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** man-template.html 1996/11/21 10:47:13 1.2
--- man-template.html 1996/12/02 18:13:42 1.3
***************
*** 34,40 ****
<hr>
<A name="adirective"><h2>ADirective</h2></A>
! <strong>Sytnax:</strong> ADirective <em>some args</em><br>
<strong>Default:</strong> <code>ADirective default value</code><br>
<strong>Context:</strong> context-list<br>
--- 34,40 ----
<hr>
<A name="adirective"><h2>ADirective</h2></A>
! <strong>Syntax:</strong> ADirective <em>some args</em><br>
<strong>Default:</strong> <code>ADirective default value</code><br>
<strong>Context:</strong> context-list<br>
1.2 +6 -6 apache/htdocs/manual/multilogs.html
Index: multilogs.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/multilogs.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** multilogs.html 1996/12/02 09:46:41 1.1
--- multilogs.html 1996/12/02 18:13:42 1.2
***************
*** 9,15 ****
<h1>Multiple Log Files</h1>
It is now possible to specify multiple log files, each with a fully
! customisable format. This is compatable with existing
configurations. Multiple log files are implemented as part of the <a
href="mod/mod_log_config.html">mod_log_config</a> module which as of
Apache 1.2 is the default log module.
--- 9,15 ----
<h1>Multiple Log Files</h1>
It is now possible to specify multiple log files, each with a fully
! customizable format. This is compatible with existing
configurations. Multiple log files are implemented as part of the <a
href="mod/mod_log_config.html">mod_log_config</a> module which as of
Apache 1.2 is the default log module.
***************
*** 23,29 ****
repeated to create more than one log file (in previous releases,
only one logfile could be given per server configuration).
The <code>TransferLog</code> directive creates a log file
! in the standard "common log format", although this can be customised
with <code>LogFormat</code>. The syntax of these two
directives is the same as for the config log module in previous
Apache releases.
--- 23,29 ----
repeated to create more than one log file (in previous releases,
only one logfile could be given per server configuration).
The <code>TransferLog</code> directive creates a log file
! in the standard "common log format", although this can be customized
with <code>LogFormat</code>. The syntax of these two
directives is the same as for the config log module in previous
Apache releases.
***************
*** 32,38 ****
The real power of multiple log files come from the ability to
create log files in different formats. For example, as well
as a CLF transfer log, the server could log the user agent of
! each client, or the referer information, or any other aspect of
the request, such as the language preferences of the user.
<p>
--- 32,38 ----
The real power of multiple log files come from the ability to
create log files in different formats. For example, as well
as a CLF transfer log, the server could log the user agent of
! each client, or the referrer information, or any other aspect of
the request, such as the language preferences of the user.
<p>
***************
*** 41,47 ****
<hr>
! <strong>Sytnax:</strong> CustomLog <em>filename "format"</em><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> base<br>
<strong>Module:</strong> mod_log_config<p>
--- 41,47 ----
<hr>
! <strong>Syntax:</strong> CustomLog <em>filename "format"</em><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> base<br>
<strong>Module:</strong> mod_log_config<p>
***************
*** 81,87 ****
CustomLog logs/agents "%{user-agent}i"
</pre>
! To define a CLF transfer log and a referer log which log
all accesses to both the main server and a virtual host:
<pre>
--- 81,87 ----
CustomLog logs/agents "%{user-agent}i"
</pre>
! To define a CLF transfer log and a referrer log which log
all accesses to both the main server and a virtual host:
<pre>
***************
*** 104,110 ****
</pre>
was added inside the virtual host definition, then accesses to this
! virtual host will be logged in vhost_acces_log file (in common
log format), and <i>not</i> in logs/access_log or logs/referer.
<!--#include virtual="footer.html" -->
--- 104,110 ----
</pre>
was added inside the virtual host definition, then accesses to this
! virtual host will be logged in vhost_access_log file (in common
log format), and <i>not</i> in logs/access_log or logs/referer.
<!--#include virtual="footer.html" -->
1.4 +2 -2 apache/htdocs/manual/new_features_1_0.html
Index: new_features_1_0.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/new_features_1_0.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** new_features_1_0.html 1996/12/01 06:38:11 1.3
--- new_features_1_0.html 1996/12/02 18:13:43 1.4
***************
*** 42,49 ****
We found that many people were using values for "MaxServers" either
too high or too low, and were hanging themselves on it. The model we
adopted is still based on long-lived minimal-forking processes, but
! instead of specifying one number of persistant processes, the
! webmaster specifies a maximum and minimum number of processes to be
"spare" - every couple of seconds the parent checks the actual number
of spare servers and adjusts accordingly. This should keep the number
of servers concurrently running relatively low while still ensuring
--- 42,49 ----
We found that many people were using values for "MaxServers" either
too high or too low, and were hanging themselves on it. The model we
adopted is still based on long-lived minimal-forking processes, but
! instead of specifying one number of persistent processes, the
! web-master specifies a maximum and minimum number of processes to be
"spare" - every couple of seconds the parent checks the actual number
of spare servers and adjusts accordingly. This should keep the number
of servers concurrently running relatively low while still ensuring
1.5 +3 -3 apache/htdocs/manual/new_features_1_1.html
Index: new_features_1_1.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/new_features_1_1.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C3 -r1.4 -r1.5
*** new_features_1_1.html 1996/12/01 06:38:11 1.4
--- new_features_1_1.html 1996/12/02 18:13:43 1.5
***************
*** 52,58 ****
<li><b><a href="mod/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
--- 52,58 ----
<li><b><a href="mod/mod_status.html">Status
Module</a></b><br>
! Apache now contains a module that gives the web-master 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
***************
*** 111,124 ****
do not support imagemaps.
<li><b><a href="mod/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>
--- 111,124 ----
do not support imagemaps.
<li><b><a href="mod/mod_userdir.html">Improved UserDir Directive</a></b><br>
! Now supports the ability to point user's files (as specified 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 supersedes the -DMINIMAL_DNS
compile-time configuration option. This option can be set per-directory.
<li><b>IdentityCheck Now Per-Directory Option</b><br>
1.14 +3 -3 apache/htdocs/manual/new_features_1_2.html
Index: new_features_1_2.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/new_features_1_2.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -C3 -r1.13 -r1.14
*** new_features_1_2.html 1996/12/02 09:46:41 1.13
--- new_features_1_2.html 1996/12/02 18:13:44 1.14
***************
*** 37,43 ****
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="mod/mod_include.html">eXtended Server Side Includes
--- 37,43 ----
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 transferring
files. Apache does, however, still work great with HTTP/1.0 browsers.
<li><b><a href="mod/mod_include.html">eXtended Server Side Includes
***************
*** 121,127 ****
processes.
<li><b><a href="mod/mod_alias.html">Redirect Directive Can Returns
Additional Statuses</a></b><br>
! The Redirect directive can return permanent or temporary redirectes,
"Gone" or "See Other" HTTP statuses. For NCSA-compatability,
RedirectTemp and RedirectPermanent are also implemented.
--- 121,127 ----
processes.
<li><b><a href="mod/mod_alias.html">Redirect Directive Can Returns
Additional Statuses</a></b><br>
! The Redirect directive can return permanent or temporary redirects,
"Gone" or "See Other" HTTP statuses. For NCSA-compatability,
RedirectTemp and RedirectPermanent are also implemented.
***************
*** 130,136 ****
Apache can re-read the config files and re-open log files without
terminating transactions in progress.
! <li><b><a href="install.html">Simplified Compliation</a></b><br>
The process of configuring Apache for compilation has been
simplified.
--- 130,136 ----
Apache can re-read the config files and re-open log files without
terminating transactions in progress.
! <li><b><a href="install.html">Simplified Compilation</a></b><br>
The process of configuring Apache for compilation has been
simplified.
1.5 +3 -3 apache/htdocs/manual/process-model.html
Index: process-model.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/process-model.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C3 -r1.4 -r1.5
*** process-model.html 1996/11/21 10:47:15 1.4
--- process-model.html 1996/12/02 18:13:44 1.5
***************
*** 10,17 ****
We found that many people were using values for "MaxServers" either
too high or too low, and were hanging themselves on it. The model we
adopted is still based on long-lived minimal-forking processes, but
! instead of specifying one number of persistant processes, the
! webmaster specifies a maximum and minimum number of processes to be
"spare" - every couple of seconds the parent checks the actual number
of spare servers and adjusts accordingly. This should keep the number
of servers concurrently running relatively low while still ensuring
--- 10,17 ----
We found that many people were using values for "MaxServers" either
too high or too low, and were hanging themselves on it. The model we
adopted is still based on long-lived minimal-forking processes, but
! instead of specifying one number of persistent processes, the
! web-master specifies a maximum and minimum number of processes to be
"spare" - every couple of seconds the parent checks the actual number
of spare servers and adjusts accordingly. This should keep the number
of servers concurrently running relatively low while still ensuring
***************
*** 22,28 ****
We renamed the current StartServers to MinSpareServers, created
separate StartServers parameter which means what it says, and renamed
MaxServers to MaxSpareServers (though the old name still works, for
! NCSA 1.4 back-combatibility). The old names were generally regarded
as too confusing.
<P>
--- 22,28 ----
We renamed the current StartServers to MinSpareServers, created
separate StartServers parameter which means what it says, and renamed
MaxServers to MaxSpareServers (though the old name still works, for
! NCSA 1.4 back-compatibility). The old names were generally regarded
as too confusing.
<P>
1.4 +7 -7 apache/htdocs/manual/suexec.html
Index: suexec.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/suexec.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** suexec.html 1996/12/02 00:50:10 1.3
--- suexec.html 1996/12/02 18:13:45 1.4
***************
*** 10,20 ****
<h3>What is suEXEC?</h3>
The <b>suEXEC</b> feature, introduced in Apache 1.2 provides the ability to
run <b>CGI</b> programs under user ids different from the user id of the
! calling webserver. Used properly, this feature can reduce considerably the
insecurity of allowing users to run CGI programs. At the same time,
improperly
configured, this facility can crash your computer, burn your house down and
steal all the money from your retirement fund. <b>:-)</b> If you aren't
! familar with managing setuid root programs and the security issues they
present, we highly recommend that you not consider using this feature.<p>
<hr>
--- 10,20 ----
<h3>What is suEXEC?</h3>
The <b>suEXEC</b> feature, introduced in Apache 1.2 provides the ability to
run <b>CGI</b> programs under user ids different from the user id of the
! calling web-server. Used properly, this feature can reduce considerably the
insecurity of allowing users to run CGI programs. At the same time,
improperly
configured, this facility can crash your computer, burn your house down and
steal all the money from your retirement fund. <b>:-)</b> If you aren't
! familiar with managing setuid root programs and the security issues they
present, we highly recommend that you not consider using this feature.<p>
<hr>
***************
*** 26,32 ****
<ul>
<h3>Configuring the suEXEC wrapper</h3>
! From the toplevel of the Apache source tree, type: <b><code>cd
support [ENTER]</code></b><p>
Edit the <code>suexec.h</code> file and change the following macros to
match your
local Apache installation.<p>
<i>From support/suexec.h</i>
--- 26,32 ----
<ul>
<h3>Configuring the suEXEC wrapper</h3>
! From the top-level of the Apache source tree, type: <b><code>cd
support [ENTER]</code></b><p>
Edit the <code>suexec.h</code> file and change the following macros to
match your
local Apache installation.<p>
<i>From support/suexec.h</i>
***************
*** 47,55 ****
#define LOG_EXEC "/usr/local/etc/httpd/logs/cgi.log"
/*
! * DOC_ROOT -- Define as the DocuemntRoot set for Apache. This
* will be the only hierarchy (aside from UserDirs)
! * that can be used for suEXEC behaviour.
*/
#define DOC_ROOT "/usr/local/etc/httpd/htdocs"
--- 47,55 ----
#define LOG_EXEC "/usr/local/etc/httpd/logs/cgi.log"
/*
! * DOC_ROOT -- Define as the DocumentRoot set for Apache. This
* will be the only hierarchy (aside from UserDirs)
! * that can be used for suEXEC behavior.
*/
#define DOC_ROOT "/usr/local/etc/httpd/htdocs"
***************
*** 117,123 ****
<li>The current working directory <b>must be a directory</b>.
<li>The current working directory <b>must not be writable by <em>group</em>
or <em>other</em></b>.
<li>The command being executed <b>cannot be a symbolic link</b>.
! <li>The command being executed <b>cannot be writeable by <em>group</em> or
<em>other</em></b>.
<li>The command being executed <b>cannot be a <em>setuid</em> or
<em>setgid</em> program</b>.
<li>The target UID and GID <b>must be a valid user and group on this
system</b>.
<li>The target UID and GID to execute as, <b>must match the UID and GID of
the directory</b>.
--- 117,123 ----
<li>The current working directory <b>must be a directory</b>.
<li>The current working directory <b>must not be writable by <em>group</em>
or <em>other</em></b>.
<li>The command being executed <b>cannot be a symbolic link</b>.
! <li>The command being executed <b>cannot be writable by <em>group</em> or
<em>other</em></b>.
<li>The command being executed <b>cannot be a <em>setuid</em> or
<em>setgid</em> program</b>.
<li>The target UID and GID <b>must be a valid user and group on this
system</b>.
<li>The target UID and GID to execute as, <b>must match the UID and GID of
the directory</b>.
***************
*** 133,139 ****
<h3>Using suEXEC</h3>
After properly installing the <b>suexec</b> wrapper executable, you must
kill and restart
the Apache server. A simple <code><b>kill -1 `cat httpd.pid`</b></code>
will not be enough.
! Upon startup of the webserver, if Apache finds a properly configured
<b>suexec</b> wrapper,
it will print the following message to the console.<p>
<code>Configuring Apache for use with suexec wrapper.</code><p>
--- 133,139 ----
<h3>Using suEXEC</h3>
After properly installing the <b>suexec</b> wrapper executable, you must
kill and restart
the Apache server. A simple <code><b>kill -1 `cat httpd.pid`</b></code>
will not be enough.
! Upon startup of the web-server, if Apache finds a properly configured
<b>suexec</b> wrapper,
it will print the following message to the console.<p>
<code>Configuring Apache for use with suexec wrapper.</code><p>
1.6 +6 -6 apache/htdocs/manual/virtual-host.html
Index: virtual-host.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/virtual-host.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -C3 -r1.5 -r1.6
*** virtual-host.html 1996/11/26 05:36:40 1.5
--- virtual-host.html 1996/12/02 18:13:45 1.6
***************
*** 13,21 ****
<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
called <code>www.serve.com</code> which provides Web space for several
! organisations including, say, <em>smallco</em> and <em>baygroup</em>.
Ordinarily, these groups would be given parts of the Web tree on
www.serve.com.
So smallco's home page would have the URL
<blockquote>
--- 13,21 ----
<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
called <code>www.serve.com</code> which provides Web space for several
! organizations including, say, <em>smallco</em> and <em>baygroup</em>.
Ordinarily, these groups would be given parts of the Web tree on
www.serve.com.
So smallco's home page would have the URL
<blockquote>
***************
*** 26,38 ****
http://www.serve.com/baygroup/
</blockquote>
<p>
! For aesthetic reasons, however, both organisations would rather their home
pages appeared under their own names rather than that of the service
! provider's; but they do not want to set up their own internet links and
servers.
<p>
Virtual hosts are the solution to this problem. smallco and baygroup would
! have their own internet name registrations, <code>www.smallco.com</code> and
<code>www.baygroup.org</code> respectively. These hostnames would both
correspond to the service provider's machine (www.serve.com). Thus
smallco's home page would now have the URL
--- 26,38 ----
http://www.serve.com/baygroup/
</blockquote>
<p>
! For esthetic reasons, however, both organizations would rather their home
pages appeared under their own names rather than that of the service
! provider's; but they do not want to set up their own Internet links and
servers.
<p>
Virtual hosts are the solution to this problem. smallco and baygroup would
! have their own Internet name registrations, <code>www.smallco.com</code> and
<code>www.baygroup.org</code> respectively. These hostnames would both
correspond to the service provider's machine (www.serve.com). Thus
smallco's home page would now have the URL
***************
*** 90,96 ****
<A HREF="mod/core.html#documentroot">DocumentRoot</A>,
<A HREF="mod/core.html#errorlog">ErrorLog</A> and
<A HREF="mod_log_common.html#transferlog">TransferLog</A> configuration
! directives to different values for each virtaul host.
e.g.
<blockquote><code>
<VirtualHost www.smallco.com><br>
--- 90,96 ----
<A HREF="mod/core.html#documentroot">DocumentRoot</A>,
<A HREF="mod/core.html#errorlog">ErrorLog</A> and
<A HREF="mod_log_common.html#transferlog">TransferLog</A> configuration
! directives to different values for each virtual host.
e.g.
<blockquote><code>
<VirtualHost www.smallco.com><br>
1.14 +11 -11 apache/htdocs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/core.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -C3 -r1.13 -r1.14
*** core.html 1996/12/02 16:53:31 1.13
--- core.html 1996/12/02 18:13:58 1.14
***************
*** 214,220 ****
The server comes with a built-in list of active modules. This
directive clears the list. It is assumed that the list will then be
! repopulated using the <A HREF="#addmodule">AddModule</A> directive.<p><hr>
<A name="bindaddress"><h2>BindAddress directive</h2></A>
<!--%plaintext <?INDEX {\tt BindAddress} directive> -->
--- 214,220 ----
The server comes with a built-in list of active modules. This
directive clears the list. It is assumed that the list will then be
! re-populated using the <A HREF="#addmodule">AddModule</A> directive.<p><hr>
<A name="bindaddress"><h2>BindAddress directive</h2></A>
<!--%plaintext <?INDEX {\tt BindAddress} directive> -->
***************
*** 271,277 ****
directives which will apply only to the named directory and sub-directories
of that directory. Any directive which is allowed in a directory
context may be used. <em>Directory</em> is either the full path to a
directory,
! or a wildcard string. In a wildcard string, `?' matches any single
character,
and `*' matches any sequences of characters. Example:
<pre>
<Directory /usr/local/httpd/htdocs>
--- 271,277 ----
directives which will apply only to the named directory and sub-directories
of that directory. Any directive which is allowed in a directory
context may be used. <em>Directory</em> is either the full path to a
directory,
! or a wild-card string. In a wild-card string, `?' matches any single
character,
and `*' matches any sequences of characters. Example:
<pre>
<Directory /usr/local/httpd/htdocs>
***************
*** 296,302 ****
<blockquote><code>
<Directory /><br>
AllowOverride None<br>
! </Directoy><br><br>
<Directory /home/*><br>
AllowOverride FileInfo<br>
</Directory></code></blockquote>
--- 296,302 ----
<blockquote><code>
<Directory /><br>
AllowOverride None<br>
! </Directory><br><br>
<Directory /home/*><br>
AllowOverride FileInfo<br>
</Directory></code></blockquote>
***************
*** 408,414 ****
read, but before <Location> sections.</p>
<p>The <em>filename</em> argument should include a filename, or a
! wildcard string, where `?' matches any single character, and `*' matches any
sequences of characters. Extended regular expressions can also be used,
with the addition of
the <code>~</code> character. For example:</p>
--- 408,414 ----
read, but before <Location> sections.</p>
<p>The <em>filename</em> argument should include a filename, or a
! wild-card string, where `?' matches any single character, and `*' matches
any
sequences of characters. Extended regular expressions can also be used,
with the addition of
the <code>~</code> character. For example:</p>
***************
*** 437,443 ****
<strong>Status:</strong> core<p>
The Group directive sets the group under which the server will answer
requests.
! In order to use this directive, the standalone server must be run initially
as root. <em>Unix-group</em> is one of:
<dl>
<dt>A group name
--- 437,443 ----
<strong>Status:</strong> core<p>
The Group directive sets the group under which the server will answer
requests.
! In order to use this directive, the stand-alone server must be run initially
as root. <em>Unix-group</em> is one of:
<dl>
<dt>A group name
***************
*** 510,516 ****
name of the module, at the time it was compiled. For example,
<code>mod_rewrite.c</code>.
! <p><IfModule> sections are nestable, which can be used to implement
simple multiple-module tests.
<P> <hr>
--- 510,516 ----
name of the module, at the time it was compiled. For example,
<code>mod_rewrite.c</code>.
! <p><IfModule> sections are nest-able, which can be used to implement
simple multiple-module tests.
<P> <hr>
***************
*** 592,598 ****
1.1 and later.<p>
<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
--- 592,598 ----
1.1 and later.<p>
<p>The <Location> directive provides for access control by
! URL. It is comparable 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
***************
*** 604,611 ****
<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.
--- 604,611 ----
<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
! necessarily have to protect a directory (it can be an individual
! file, or a number of files), and can include wild-cards. In a wild-card
string, `?' matches any single character, and `*' matches any
sequences of characters.
***************
*** 746,752 ****
<dt>MultiViews
<dd>
<!--%plaintext <?INDEX {\tt MultiViews} option> -->
! <A HREF="content-negotiation.html">Ccontent negotiatad</A> MultiViews are
allowed.
<dt>SymLinksIfOwnerMatch
<dd>
--- 746,752 ----
<dt>MultiViews
<dd>
<!--%plaintext <?INDEX {\tt MultiViews} option> -->
! <A HREF="content-negotiation.html">Content negotiated</A> MultiViews are
allowed.
<dt>SymLinksIfOwnerMatch
<dd>
***************
*** 948,954 ****
Process limits control the number of processes per user.<p>
Note: If CGI processes are <b>not</b> running under userids other than the
! webserver userid, this directive will limit the number of processes that the
server itself can create. Evidence of this situation will be indicated by
<b><em>cannot fork</em></b> messages in the error_log.<p>
--- 948,954 ----
Process limits control the number of processes per user.<p>
Note: If CGI processes are <b>not</b> running under userids other than the
! web server userid, this directive will limit the number of processes that
the
server itself can create. Evidence of this situation will be indicated by
<b><em>cannot fork</em></b> messages in the error_log.<p>
1.7 +2 -2 apache/htdocs/manual/mod/index.html
Index: index.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/index.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -C3 -r1.6 -r1.7
*** index.html 1996/11/25 13:56:39 1.6
--- index.html 1996/12/02 18:13:58 1.7
***************
*** 16,22 ****
<dt><A HREF="mod_actions.html">mod_actions</A> Apache 1.1 and later.
<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>
--- 16,22 ----
<dt><A HREF="mod_actions.html">mod_actions</A> Apache 1.1 and later.
<dd>Filetype/method-based script execution
<dt><A HREF="mod_alias.html">mod_alias</A>
! <dd>Aliases 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>
***************
*** 70,76 ****
<dt><A HREF="mod_mime.html">mod_mime</A>
<dd>Determining document types.
<dt><A HREF="mod_negotiation.html">mod_negotiation</A>
! <dd>Content negotation.
<dt><A NAME="mod_rewrite.html">mod_rewrite</a> Apache 1.2 and up
<dd>Powerful URI-to-filename mapping using regular expressions
<dt><A HREF="mod_proxy.html">mod_proxy</A>
--- 70,76 ----
<dt><A HREF="mod_mime.html">mod_mime</A>
<dd>Determining document types.
<dt><A HREF="mod_negotiation.html">mod_negotiation</A>
! <dd>Content negotiation.
<dt><A NAME="mod_rewrite.html">mod_rewrite</a> Apache 1.2 and up
<dd>Powerful URI-to-filename mapping using regular expressions
<dt><A HREF="mod_proxy.html">mod_proxy</A>
1.3 +2 -2 apache/htdocs/manual/mod/mod_actions.html
Index: mod_actions.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_actions.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_actions.html 1996/11/21 10:30:37 1.2
--- mod_actions.html 1996/12/02 18:13:59 1.3
***************
*** 29,35 ****
<A name="action"><h2>Action</h2></A>
<strong>Syntax:</strong> Action <em>mime-type cgi-script</em><br>
! <strong>Context:</strong> server config, virutal host, directory,
.htaccess<br>
<strong>Override:</strong> FileInfo<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_actions<br>
--- 29,35 ----
<A name="action"><h2>Action</h2></A>
<strong>Syntax:</strong> Action <em>mime-type cgi-script</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_actions<br>
***************
*** 45,51 ****
<A name="script"><h2>Script</h2></A>
<strong>Syntax:</strong> Script <em>method cgi-script</em><br>
! <strong>Context:</strong> server config, virutal host, directory<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_actions<br>
<strong>Compatibility:</strong> Script is only available in Apache 1.1
--- 45,51 ----
<A name="script"><h2>Script</h2></A>
<strong>Syntax:</strong> Script <em>method cgi-script</em><br>
! <strong>Context:</strong> server config, virtual host, directory<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_actions<br>
<strong>Compatibility:</strong> Script is only available in Apache 1.1
1.6 +1 -1 apache/htdocs/manual/mod/mod_alias.html
Index: mod_alias.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_alias.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -C3 -r1.5 -r1.6
*** mod_alias.html 1996/12/01 06:44:39 1.5
--- mod_alias.html 1996/12/02 18:13:59 1.6
***************
*** 114,120 ****
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_alias<br>
! The ScriptAlias directive has the same behaviour as the
<A HREF="#alias">Alias</A> directive, except that in addition it
marks the target directory as containing CGI scripts.
URLs with a (%-decoded) path beginning with <em>url-path</em> will be
--- 114,120 ----
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_alias<br>
! The ScriptAlias directive has the same behavior as the
<A HREF="#alias">Alias</A> directive, except that in addition it
marks the target directory as containing CGI scripts.
URLs with a (%-decoded) path beginning with <em>url-path</em> will be
1.3 +3 -3 apache/htdocs/manual/mod/mod_auth.html
Index: mod_auth.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_auth.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_auth.html 1996/11/21 10:30:39 1.2
--- mod_auth.html 1996/12/02 18:14:00 1.3
***************
*** 40,46 ****
be used instead.<p>
Security: make sure that the AuthGroupFile is stored outside the
! document tree of the webserver; do <em>not</em> put it in the directory that
it protects. Otherwise, clients will be able to download the
AuthGroupFile.<p>
See also <A HREF="core.html#authname">AuthName</A>,
--- 40,46 ----
be used instead.<p>
Security: make sure that the AuthGroupFile is stored outside the
! document tree of the web-server; do <em>not</em> put it in the directory
that
it protects. Otherwise, clients will be able to download the
AuthGroupFile.<p>
See also <A HREF="core.html#authname">AuthName</A>,
***************
*** 59,72 ****
of users and passwords for user authentication. <em>Filename</em> is the
absolute path to the user file.<p>
Each line of the user file file contains a username followed by a colon,
! followed by the crypt() encrypted password. The behaviour of multiple
occurrences of the same user is undefined.<p>
Note that searching user groups files is inefficient;
<A HREF="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</A> should
be used instead.<p>
Security: make sure that the AuthUserFile is stored outside the
! document tree of the webserver; do <em>not</em> put it in the directory that
it protects. Otherwise, clients will be able to download the
AuthUserFile.<p>
See also <A HREF="core.html#authname">AuthName</A>,
--- 59,72 ----
of users and passwords for user authentication. <em>Filename</em> is the
absolute path to the user file.<p>
Each line of the user file file contains a username followed by a colon,
! followed by the crypt() encrypted password. The behavior of multiple
occurrences of the same user is undefined.<p>
Note that searching user groups files is inefficient;
<A HREF="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</A> should
be used instead.<p>
Security: make sure that the AuthUserFile is stored outside the
! document tree of the web-server; do <em>not</em> put it in the directory
that
it protects. Otherwise, clients will be able to download the
AuthUserFile.<p>
See also <A HREF="core.html#authname">AuthName</A>,
1.3 +4 -4 apache/htdocs/manual/mod/mod_auth_anon.html
Index: mod_auth_anon.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_auth_anon.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_auth_anon.html 1996/11/21 10:30:40 1.2
--- mod_auth_anon.html 1996/12/02 18:14:01 1.3
***************
*** 67,73 ****
</code></dt><dd>
When set 'on', the default is 'off', the 'password' entered is
checked for at least one '@' and a '.' to encourage users to enter
! valid email addressses (see the above <code>Auth_LogEmail</code>.
</dd>
<code><dt>
--- 67,73 ----
</code></dt><dd>
When set 'on', the default is 'off', the 'password' entered is
checked for at least one '@' and a '.' to encourage users to enter
! valid email addresses (see the above <code>Auth_LogEmail</code>.
</dd>
<code><dt>
***************
*** 121,127 ****
(<code>Anonymous_LogEmail</code>)
</ul>
<p>
! Excerp of access.conf:
<dl>
<dt><code>
Anonymous anonymous guest www test welcome<p>
--- 121,127 ----
(<code>Anonymous_LogEmail</code>)
</ul>
<p>
! Excerpt of access.conf:
<dl>
<dt><code>
Anonymous anonymous guest www test welcome<p>
***************
*** 162,168 ****
</dd>
<dt>Version 0.5<br></dt>
<dd>Added 'VerifyEmail' and 'LogEmail' options. Multiple
! 'anonymous' tokes allowed. more docs. Added Authorative
functionality.
</dd>
</dl>
--- 162,168 ----
</dd>
<dt>Version 0.5<br></dt>
<dd>Added 'VerifyEmail' and 'LogEmail' options. Multiple
! 'anonymous' tokens allowed. more docs. Added Authorative
functionality.
</dd>
</dl>
***************
*** 173,179 ****
This module was written for the
<a href="http://ewse.ceo.org";>European Wide Service Exchange</a> by
<<a href="mailto:[EMAIL PROTECTED]"><code>[EMAIL PROTECTED]</code></a>>.
! Feel free to contact me if you have any problems, icecreams or bugs. This
documentation, courtesy of Nick Himba, <a href="mailto:[EMAIL PROTECTED]">
<code><[EMAIL PROTECTED]></code></a>.
<p>
--- 173,179 ----
This module was written for the
<a href="http://ewse.ceo.org";>European Wide Service Exchange</a> by
<<a href="mailto:[EMAIL PROTECTED]"><code>[EMAIL PROTECTED]</code></a>>.
! Feel free to contact me if you have any problems, ice-creams or bugs. This
documentation, courtesy of Nick Himba, <a href="mailto:[EMAIL PROTECTED]">
<code><[EMAIL PROTECTED]></code></a>.
<p>
1.4 +3 -3 apache/htdocs/manual/mod/mod_auth_db.html
Index: mod_auth_db.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_auth_db.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** mod_auth_db.html 1996/11/21 10:30:41 1.3
--- mod_auth_db.html 1996/12/02 18:14:01 1.4
***************
*** 39,45 ****
be no whitespace within the value, and it must never contain any colons.<p>
Security: make sure that the AuthDBGroupFile is stored outside the
! document tree of the webserver; do <em>not</em> put it in the directory that
it protects. Otherwise, clients will be able to download the
AuthDBGroupFile unless otherwise protected.<p>
--- 39,45 ----
be no whitespace within the value, and it must never contain any colons.<p>
Security: make sure that the AuthDBGroupFile is stored outside the
! document tree of the web-server; do <em>not</em> put it in the directory
that
it protects. Otherwise, clients will be able to download the
AuthDBGroupFile unless otherwise protected.<p>
***************
*** 58,64 ****
The key for the single DB record is the username. The value consists of <p>
<blockquote><code>
! Unix Crypted Password : List of Groups [ : (ignored) ]
</code></blockquote>
The password section contains the Unix crypt() password as before. This is
--- 58,64 ----
The key for the single DB record is the username. The value consists of <p>
<blockquote><code>
! Unix Crypt-ed Password : List of Groups [ : (ignored) ]
</code></blockquote>
The password section contains the Unix crypt() password as before. This is
***************
*** 88,94 ****
by the server.<p>
Security: make sure that the AuthDBUserFile is stored outside the
! document tree of the webserver; do <em>not</em> put it in the directory that
it protects. Otherwise, clients will be able to download the
AuthDBUserFile.<p>
--- 88,94 ----
by the server.<p>
Security: make sure that the AuthDBUserFile is stored outside the
! document tree of the web-server; do <em>not</em> put it in the directory
that
it protects. Otherwise, clients will be able to download the
AuthDBUserFile.<p>
1.4 +3 -3 apache/htdocs/manual/mod/mod_auth_dbm.html
Index: mod_auth_dbm.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_auth_dbm.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** mod_auth_dbm.html 1996/11/21 10:30:41 1.3
--- mod_auth_dbm.html 1996/12/02 18:14:02 1.4
***************
*** 38,44 ****
be no whitespace within the value, and it must never contain any colons.<p>
Security: make sure that the AuthDBMGroupFile is stored outside the
! document tree of the webserver; do <em>not</em> put it in the directory that
it protects. Otherwise, clients will be able to download the
AuthDBMGroupFile unless otherwise protected.<p>
--- 38,44 ----
be no whitespace within the value, and it must never contain any colons.<p>
Security: make sure that the AuthDBMGroupFile is stored outside the
! document tree of the web-server; do <em>not</em> put it in the directory
that
it protects. Otherwise, clients will be able to download the
AuthDBMGroupFile unless otherwise protected.<p>
***************
*** 57,63 ****
The key for the single DBM is the username. The value consists of <p>
<blockquote><code>
! Unix Crypted Password : List of Groups [ : (ignored) ]
</code></blockquote>
The password section contains the Unix crypt() password as before. This is
--- 57,63 ----
The key for the single DBM is the username. The value consists of <p>
<blockquote><code>
! Unix Crypt-ed Password : List of Groups [ : (ignored) ]
</code></blockquote>
The password section contains the Unix crypt() password as before. This is
***************
*** 88,94 ****
by the server.<p>
Security: make sure that the AuthDBMUserFile is stored outside the
! document tree of the webserver; do <em>not</em> put it in the directory that
it protects. Otherwise, clients will be able to download the
AuthDBMUserFile.<p>
--- 88,94 ----
by the server.<p>
Security: make sure that the AuthDBMUserFile is stored outside the
! document tree of the web-server; do <em>not</em> put it in the directory
that
it protects. Otherwise, clients will be able to download the
AuthDBMUserFile.<p>
1.3 +16 -16 apache/htdocs/manual/mod/mod_auth_msql.html
Index: mod_auth_msql.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_auth_msql.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_auth_msql.html 1996/11/21 10:30:42 1.2
--- mod_auth_msql.html 1996/12/02 18:14:02 1.3
***************
*** 30,36 ****
</code></dt><dd>
Hostname of the machine running the mSQL demon. The effective uid
of the server should be allowed access. If not given, or if it is
! the magic name <code>localhost</code>, it is passed to the mSQL
libary as a null
pointer. This effectively forces it to use /dev/msql rather than the
(slower) socket communication.
</dd>
--- 30,36 ----
</code></dt><dd>
Hostname of the machine running the mSQL demon. The effective uid
of the server should be allowed access. If not given, or if it is
! the magic name <code>localhost</code>, it is passed to the mSQL
library as a null
pointer. This effectively forces it to use /dev/msql rather than the
(slower) socket communication.
</dd>
***************
*** 75,81 ****
Auth_MSQLuid_field < mSQL field name >
</code></dt><dd>
Name of the field containing the username in the <code>
! Auth_MSQLpwd_table</code> and optionaly in the <code>
Auth_MSQLgrp_table</code> tables.
</dd>
--- 75,81 ----
Auth_MSQLuid_field < mSQL field name >
</code></dt><dd>
Name of the field containing the username in the <code>
! Auth_MSQLpwd_table</code> and optionally in the <code>
Auth_MSQLgrp_table</code> tables.
</dd>
***************
*** 117,123 ****
not in the right group) or has the password wrong, then
he or she is denied access. When this directive is set to
'off', control is passed on to any other authorization
! modules, such as the basic auth module wih the htpasswd
file or the Unix-(g)dbm modules. The default is 'on'
to avoid nasty 'fall-through' surprises. Be sure you
know what you are doing when you decide to switch it off.
--- 117,123 ----
not in the right group) or has the password wrong, then
he or she is denied access. When this directive is set to
'off', control is passed on to any other authorization
! modules, such as the basic auth module with the htpasswd
file or the Unix-(g)dbm modules. The default is 'on'
to avoid nasty 'fall-through' surprises. Be sure you
know what you are doing when you decide to switch it off.
***************
*** 127,133 ****
Auth_MSQL_EncryptedPasswords < on | off >
</code></dt><dd>
Default is 'on'. When set on, the values in the
! pwd_field are assumed to be crypted using *your*
machines 'crypt()' function and the incoming password
is 'crypt'ed before comparison. When this function is
'off', the comparison is done directly with the plaintext
--- 127,133 ----
Auth_MSQL_EncryptedPasswords < on | off >
</code></dt><dd>
Default is 'on'. When set on, the values in the
! pwd_field are assumed to be crypt-ed using *your*
machines 'crypt()' function and the incoming password
is 'crypt'ed before comparison. When this function is
'off', the comparison is done directly with the plaintext
***************
*** 230,236 ****
Auth_MSQLgrp_table user_records <br>
Auth_MSQLgrp_field Xgroup <br>
</code></dt><dd>
! Optionaly one can also specify a table which contains the
user/group combinations. This can be the same table which
also contains the username/password combinations. However
if a user belongs to two or more groups, one will have to
--- 230,236 ----
Auth_MSQLgrp_table user_records <br>
Auth_MSQLgrp_field Xgroup <br>
</code></dt><dd>
! Optionally one can also specify a table which contains the
user/group combinations. This can be the same table which
also contains the username/password combinations. However
if a user belongs to two or more groups, one will have to
***************
*** 290,302 ****
not have the uid field as a primary key, it is possible for the
uid to occur more than once in the table with possibly different
passwords. When this module is compiled with the <code>ONLY_ONCE</code>
! directive set, access is denied if the uid occures more than once in the
uid/passwd table. If you choose not to set it, the software takes
the first pair returned and ignores any further pairs. The SQL
statement used for this is<br>
<p><code>"select password form pwd_table where user='uid'"</code><p>
this might lead to unpredictable results. For this reason as well
! as for performance reasons you are strongly adviced to make the
uid field a primary key. Use at your own peril :-)
</dd>
--- 290,302 ----
not have the uid field as a primary key, it is possible for the
uid to occur more than once in the table with possibly different
passwords. When this module is compiled with the <code>ONLY_ONCE</code>
! directive set, access is denied if the uid occurs more than once in the
uid/passwd table. If you choose not to set it, the software takes
the first pair returned and ignores any further pairs. The SQL
statement used for this is<br>
<p><code>"select password form pwd_table where user='uid'"</code><p>
this might lead to unpredictable results. For this reason as well
! as for performance reasons you are strongly advised to make the
uid field a primary key. Use at your own peril :-)
</dd>
***************
*** 304,321 ****
<a name="KEEP_MSQL_CONNECTION_OPEN">#define KEEP_MSQL_CONNECTION_OPEN</a>
</code></dt><dd>
Normally the (tcp/ip) connection with the database is opened and
! closed for each SQL query. When the Apache webserver and the database
are on the same machine, and /dev/msql is used this does not
cause a serious overhead. However when your platform does not
support this (see the mSQL documentation) or when the web server
and the database are on different machines the overhead can be
considerable. When the above directive is set defined the server leaves
the connection open, i.e. no call to <code>msqlClose()</code>.
! If an error occures an attempt is made to reopen the connection for
the next http request.
<p>
This has a number of very serious drawbacks
! <ul><li> It costs 2 already rare filedescriptors for each child.
<li> It costs msql-connections, typically one per child. The
(compiled in)
number of connections mSQL can handle is low, typically 6 or 12.
which might prohibit access to the mSQL database for later
--- 304,321 ----
<a name="KEEP_MSQL_CONNECTION_OPEN">#define KEEP_MSQL_CONNECTION_OPEN</a>
</code></dt><dd>
Normally the (tcp/ip) connection with the database is opened and
! closed for each SQL query. When the Apache web-server and the database
are on the same machine, and /dev/msql is used this does not
cause a serious overhead. However when your platform does not
support this (see the mSQL documentation) or when the web server
and the database are on different machines the overhead can be
considerable. When the above directive is set defined the server leaves
the connection open, i.e. no call to <code>msqlClose()</code>.
! If an error occurs an attempt is made to reopen the connection for
the next http request.
<p>
This has a number of very serious drawbacks
! <ul><li> It costs 2 already rare file-descriptors for each child.
<li> It costs msql-connections, typically one per child. The
(compiled in)
number of connections mSQL can handle is low, typically 6 or 12.
which might prohibit access to the mSQL database for later
***************
*** 323,332 ****
<li> When a child dies, it might not free that connection properly
or quick enough.
<li> When errors start to occur, connection/file-descriptor resources
! might become exausted very quickly.
</ul>
<p>
! In short, use this at your own peril and only in a highly controled and
monitored environment.
</dd>
--- 323,332 ----
<li> When a child dies, it might not free that connection properly
or quick enough.
<li> When errors start to occur, connection/file-descriptor resources
! might become exhausted very quickly.
</ul>
<p>
! In short, use this at your own peril and only in a highly controlled and
monitored environment.
</dd>
***************
*** 339,356 ****
A second mSQL auth module for Apache has also been developed by Vivek
Khera
<<a
href="mailto:khera@kciLink.com";><code>khera@kciLink.com</code></a>>
and was subsequently distributed with some early versions of Apache. It
! can be optained from
<code><a
href="ftp://ftp.kcilink.com/pub/";>ftp://ftp.kcilink.com/pub/mod_auth_msql.c*</a></code>.
Older 'vitek' versions had the field/table names compiled in. Newer
versions, v.1.11 have more <code>access.conf</code> configuration
! options. However these where choosen not to be in line the 'ewse'
version of this module. Also, the 'vitek' module does not give group
control or 'empty' password control.
<p>
To get things slightly more in line this version (0.9) should
be backward compatible with the 'vitek' module by:
<ul><li> Adding support for the
<code>Auth_MSQL_EncryptedPasswords</code> on/off functionality
! <li> Adding support for the different spelling fo the 4 configuration
tokens for user-table-name, user/password-field-name and
dbase-name.
<li> Setting some field names to a default which used to be hard
coded in in older 'vitek' modules.
--- 339,356 ----
A second mSQL auth module for Apache has also been developed by Vivek
Khera
<<a
href="mailto:khera@kciLink.com";><code>khera@kciLink.com</code></a>>
and was subsequently distributed with some early versions of Apache. It
! can be obtained from
<code><a
href="ftp://ftp.kcilink.com/pub/";>ftp://ftp.kcilink.com/pub/mod_auth_msql.c*</a></code>.
Older 'vitek' versions had the field/table names compiled in. Newer
versions, v.1.11 have more <code>access.conf</code> configuration
! options. However these where chosen not to be in line the 'ewse'
version of this module. Also, the 'vitek' module does not give group
control or 'empty' password control.
<p>
To get things slightly more in line this version (0.9) should
be backward compatible with the 'vitek' module by:
<ul><li> Adding support for the
<code>Auth_MSQL_EncryptedPasswords</code> on/off functionality
! <li> Adding support for the different spelling of the 4 configuration
tokens for user-table-name, user/password-field-name and
dbase-name.
<li> Setting some field names to a default which used to be hard
coded in in older 'vitek' modules.
***************
*** 438,444 ****
This module was written for the
<a href="http://ewse.ceo.org";>European Wide Service Exchange</a> by
<<a href="mailto:[EMAIL PROTECTED]"><code>[EMAIL PROTECTED]</code></a>>.
! Feel free to contact me if you have any problems, icecreams or bugs. This
documentation, courtesy of Nick Himba, <a href="mailto:[EMAIL PROTECTED]">
<code><[EMAIL PROTECTED]></code></a>.
<p>
--- 438,444 ----
This module was written for the
<a href="http://ewse.ceo.org";>European Wide Service Exchange</a> by
<<a href="mailto:[EMAIL PROTECTED]"><code>[EMAIL PROTECTED]</code></a>>.
! Feel free to contact me if you have any problems, ice-creams or bugs. This
documentation, courtesy of Nick Himba, <a href="mailto:[EMAIL PROTECTED]">
<code><[EMAIL PROTECTED]></code></a>.
<p>
1.6 +2 -2 apache/htdocs/manual/mod/mod_browser.html
Index: mod_browser.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_browser.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -C3 -r1.5 -r1.6
*** mod_browser.html 1996/12/01 08:40:01 1.5
--- mod_browser.html 1996/12/02 18:14:03 1.6
***************
*** 29,35 ****
<hr>
<A name="browsermatch"><h2>BrowserMatch</h2></A>
! <strong>Sytnax:</strong> BrowserMatch <em>regex attr1 attr2...</em><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> base<br>
<strong>Module:</strong> mod_browser<br>
--- 29,35 ----
<hr>
<A name="browsermatch"><h2>BrowserMatch</h2></A>
! <strong>Syntax:</strong> BrowserMatch <em>regex attr1 attr2...</em><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> base<br>
<strong>Module:</strong> mod_browser<br>
***************
*** 56,62 ****
</pre>
<p><A name="browsermatchnocase"><h2>BrowserMatchNoCase</h2></A>
! <strong>Sytnax:</strong> BrowserMatchNoCase <em>regex attr1
attr2...</em><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> base<br>
<strong>Module:</strong> mod_browser<br>
--- 56,62 ----
</pre>
<p><A name="browsermatchnocase"><h2>BrowserMatchNoCase</h2></A>
! <strong>Syntax:</strong> BrowserMatchNoCase <em>regex attr1
attr2...</em><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> base<br>
<strong>Module:</strong> mod_browser<br>
1.5 +2 -2 apache/htdocs/manual/mod/mod_cgi.html
Index: mod_cgi.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_cgi.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C3 -r1.4 -r1.5
*** mod_cgi.html 1996/11/28 07:42:17 1.4
--- mod_cgi.html 1996/12/02 18:14:03 1.5
***************
*** 33,39 ****
<h2>CGI Environment variables</h2>
The server will set the CGI environment variables as described in the CGI
! specification, with the following provisos:
<dl>
<dt>REMOTE_HOST
<dd>This will only be set if the server has not been compiled with
--- 33,39 ----
<h2>CGI Environment variables</h2>
The server will set the CGI environment variables as described in the CGI
! specification, with the following provisons:
<dl>
<dt>REMOTE_HOST
<dd>This will only be set if the server has not been compiled with
***************
*** 135,141 ****
script logfile. Since the logfile logs a lot of information per CGI
error (all request headers, all script output) it can grow to be a big
file. To prevent problems due to unbounded growth, this directive can
! be used to set an maximum filesize for the CGI logfile. If the file
exceeds this size, no more information will be written to it.
<a name="scriptlogbuffer"><h3>ScriptLogBuffer</h3></a>
--- 135,141 ----
script logfile. Since the logfile logs a lot of information per CGI
error (all request headers, all script output) it can grow to be a big
file. To prevent problems due to unbounded growth, this directive can
! be used to set an maximum file-size for the CGI logfile. If the file
exceeds this size, no more information will be written to it.
<a name="scriptlogbuffer"><h3>ScriptLogBuffer</h3></a>
1.3 +1 -1 apache/htdocs/manual/mod/mod_digest.html
Index: mod_digest.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_digest.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_digest.html 1996/11/21 10:30:44 1.2
--- mod_digest.html 1996/12/02 18:14:04 1.3
***************
*** 49,55 ****
works with supporting browsers. As of this writing (July 1996), the
majority of browsers do not support digest authentication. Therefore, we
do not reccomend using this feature on a large Internet site. However, for
! personal and intranet use, where browser users can be controlled, it is
ideal.</p>
<!--#include virtual="footer.html" -->
--- 49,55 ----
works with supporting browsers. As of this writing (July 1996), the
majority of browsers do not support digest authentication. Therefore, we
do not reccomend using this feature on a large Internet site. However, for
! personal and intra-net use, where browser users can be controlled, it is
ideal.</p>
<!--#include virtual="footer.html" -->
1.3 +2 -2 apache/htdocs/manual/mod/mod_dir.html
Index: mod_dir.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_dir.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_dir.html 1996/11/21 10:30:45 1.2
--- mod_dir.html 1996/12/02 18:14:04 1.3
***************
*** 55,61 ****
This sets the description to display for a file, for
<A HREF="#fancyindexing">FancyIndexing</A>. <em>File</em> is a file
! extension, partial filename, wildcard expression or full filename for files
to describe. <em>String</em> is enclosed in double quotes
(<code>"</code>). Example:
<blockquote><code>AddDescription "The planet Mars" /web/pics/mars.gif
--- 55,61 ----
This sets the description to display for a file, for
<A HREF="#fancyindexing">FancyIndexing</A>. <em>File</em> is a file
! extension, partial filename, wild-card expression or full filename for files
to describe. <em>String</em> is enclosed in double quotes
(<code>"</code>). Example:
<blockquote><code>AddDescription "The planet Mars" /web/pics/mars.gif
***************
*** 231,237 ****
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_dir<p>
! The IndexOptions directive specifies the behaviour of the directory
indexing.
<em>Option</em> can be one of
<dl>
<dt>FancyIndexing
--- 231,237 ----
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_dir<p>
! The IndexOptions directive specifies the behavior of the directory indexing.
<em>Option</em> can be one of
<dl>
<dt>FancyIndexing
1.3 +3 -3 apache/htdocs/manual/mod/mod_env.html
Index: mod_env.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_env.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_env.html 1996/11/21 10:30:46 1.2
--- mod_env.html 1996/12/02 18:14:05 1.3
***************
*** 17,24 ****
This module allows Apache's CGI and SSI environment to inherit
environment variables from the shell which invoked the httpd process.
! CERN webservers are able to do this, so this module is especially
! useful to webadmins who wish to migrate from CERN to Apache without
rewriting all their scripts
<h2>Directives</h2>
--- 17,24 ----
This module allows Apache's CGI and SSI environment to inherit
environment variables from the shell which invoked the httpd process.
! CERN web-servers are able to do this, so this module is especially
! useful to web-admins who wish to migrate from CERN to Apache without
rewriting all their scripts
<h2>Directives</h2>
***************
*** 37,43 ****
<strong>Compatibility:</strong> PassEnv is only available in
Apache 1.1 and later.<p>
! Passes an environment variable to CGI scripts from the servers's own
environment. Example:
<pre>
PassEnv LD_LIBRARY_PATH
--- 37,43 ----
<strong>Compatibility:</strong> PassEnv is only available in
Apache 1.1 and later.<p>
! Passes an environment variable to CGI scripts from the server's own
environment. Example:
<pre>
PassEnv LD_LIBRARY_PATH
1.4 +2 -2 apache/htdocs/manual/mod/mod_fastcgi.html
Index: mod_fastcgi.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_fastcgi.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** mod_fastcgi.html 1996/11/28 06:56:45 1.3
--- mod_fastcgi.html 1996/12/02 18:14:05 1.4
***************
*** 145,151 ****
To avoid this problem place a <code>FastCgiIpcDir</code> directive
before the <code>AppClass</code> directives in your server
! configuration. Specify a directory that's readable, writeable,
and searchable by the account you use for your Web server, but
otherwise not accessible to anyone.<p>
--- 145,151 ----
To avoid this problem place a <code>FastCgiIpcDir</code> directive
before the <code>AppClass</code> directives in your server
! configuration. Specify a directory that's readable, writable,
and searchable by the account you use for your Web server, but
otherwise not accessible to anyone.<p>
***************
*** 334,340 ****
# the socket files stored locally, in /tmp.
# FastCgiIpcDir $APACHE/logs
! # Start the echo.fcg application (echo.fcg is a symlink to echo,
# created by $FASTCGI/examples/Makefile.)
AppClass $FASTCGI/examples/echo.fcg -initial-env STATE=TEXAS
--- 334,340 ----
# the socket files stored locally, in /tmp.
# FastCgiIpcDir $APACHE/logs
! # Start the echo.fcg application (echo.fcg is a sym-link to echo,
# created by $FASTCGI/examples/Makefile.)
AppClass $FASTCGI/examples/echo.fcg -initial-env STATE=TEXAS
1.2 +4 -4 apache/htdocs/manual/mod/mod_headers.html
Index: mod_headers.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_headers.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_headers.html 1996/11/25 11:54:11 1.1
--- mod_headers.html 1996/12/02 18:14:06 1.2
***************
*** 8,14 ****
<!--#include virtual="header.html" -->
<h1>Headers Module</h1>
! The optional headers module allows for the customisation of HTTP
response headers. Headers can be merged, replaced or removed. The
directives described in this document are only available if Apache is
compiled with <b>mod_headers.c</b>.
--- 8,14 ----
<!--#include virtual="header.html" -->
<h1>Headers Module</h1>
! The optional headers module allows for the customization of HTTP
response headers. Headers can be merged, replaced or removed. The
directives described in this document are only available if Apache is
compiled with <b>mod_headers.c</b>.
***************
*** 23,30 ****
<hr>
<A name="header"><h2>Header</h2></A>
! <strong>Sytnax:</strong> Header [ set | append | add ] <em>header</em>
<em>value</em><br>
! <strong>Sytnax:</strong> Header unset <em>header</em><br>
<strong>Context:</strong> server config, virtual host, access.conf,
.htaccess<br>
<strong>Status:</strong> optional<br>
<strong>Module:</strong> mod_header<p>
--- 23,30 ----
<hr>
<A name="header"><h2>Header</h2></A>
! <strong>Syntax:</strong> Header [ set | append | add ] <em>header</em>
<em>value</em><br>
! <strong>Syntax:</strong> Header unset <em>header</em><br>
<strong>Context:</strong> server config, virtual host, access.conf,
.htaccess<br>
<strong>Status:</strong> optional<br>
<strong>Module:</strong> mod_header<p>
***************
*** 46,52 ****
<li><b>add</b><br>
The response header is added to the existing set of headers, even if
this header already exists. This can result in two (or more) headers
! having the same name. This can lead to unforseen consequences, and in
general "append" should be used instead.
<li><b>unset</b><br>
--- 46,52 ----
<li><b>add</b><br>
The response header is added to the existing set of headers, even if
this header already exists. This can result in two (or more) headers
! having the same name. This can lead to unforeseen consequences, and in
general "append" should be used instead.
<li><b>unset</b><br>
1.3 +5 -5 apache/htdocs/manual/mod/mod_imap.html
Index: mod_imap.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_imap.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_imap.html 1996/11/21 10:30:47 1.2
--- mod_imap.html 1996/12/02 18:14:06 1.3
***************
*** 59,65 ****
<p>
<A name="imapmenu"><h3>ImapMenu</h3></A>
! <strong>Syntax:</strong> ImapMenu <code>{none, formatted, semiformatted,
unformatted}</code><br>
<Strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
<Strong>Override:</strong> Indexes<br>
--- 59,65 ----
<p>
<A name="imapmenu"><h3>ImapMenu</h3></A>
! <strong>Syntax:</strong> ImapMenu <code>{none, formatted, semi-formatted,
unformatted}</code><br>
<Strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
<Strong>Override:</strong> Indexes<br>
***************
*** 142,148 ****
<code>poly</code>, <code>circle</code>, <code>rect</code>, or
<code>point</code>. The value is an absolute or relative URL, or one
of the special values listed below. The coordinates are
! <code>x,y</code> pairs seperated by whitespace. The quoted text is
used as the text of the link if a imagemap menu is generated. Lines
beginning with '#' are comments.
--- 142,148 ----
<code>poly</code>, <code>circle</code>, <code>rect</code>, or
<code>point</code>. The value is an absolute or relative URL, or one
of the special values listed below. The coordinates are
! <code>x,y</code> pairs separated by whitespace. The quoted text is
used as the text of the link if a imagemap menu is generated. Lines
beginning with '#' are comments.
***************
*** 153,159 ****
<dl>
<dt><code>base</code> Directive
<dd>Has the effect of <code><BASE href="value"></code>. The
! non-absolute URLs of the mapfile are taken relative to this value.
The <code>base</code> directive overrides ImapBase as set in a
.htaccess file or in the server configuration files. In the absence
of an ImapBase configuration directive, <code>base</code> defaults to
--- 153,159 ----
<dl>
<dt><code>base</code> Directive
<dd>Has the effect of <code><BASE href="value"></code>. The
! non-absolute URLs of the map-file are taken relative to this value.
The <code>base</code> directive overrides ImapBase as set in a
.htaccess file or in the server configuration files. In the absence
of an ImapBase configuration directive, <code>base</code> defaults to
***************
*** 211,217 ****
<dd>Synonymous with <code>map</code>.
<p>
<dt><code>referer</code>
! <dd>Equivalent to the URL of the refering document.
Defaults to <code>http://servername/</code> if no Referer:
header was present.
<p>
--- 211,217 ----
<dd>Synonymous with <code>map</code>.
<p>
<dt><code>referer</code>
! <dd>Equivalent to the URL of the referring document.
Defaults to <code>http://servername/</code> if no Referer:
header was present.
<p>
***************
*** 231,237 ****
<dt><code>0,0 200,200</code>
<dd>A coordinate consists of an <tt>x</tt> and a <tt>y</tt> value
separated by a comma. The coordinates are separated from each other
! by whitespace. To accomodate the way Lynx handles imagemaps, should
a
user select the coordinate <code>0,0</code>, it is as if
no coordinate had been selected.
</dl>
--- 231,237 ----
<dt><code>0,0 200,200</code>
<dd>A coordinate consists of an <tt>x</tt> and a <tt>y</tt> value
separated by a comma. The coordinates are separated from each other
! by whitespace. To accommodate the way Lynx handles imagemaps,
should a
user select the coordinate <code>0,0</code>, it is as if
no coordinate had been selected.
</dl>
1.4 +2 -2 apache/htdocs/manual/mod/mod_include.html
Index: mod_include.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_include.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** mod_include.html 1996/11/28 04:08:38 1.3
--- mod_include.html 1996/12/02 18:14:08 1.4
***************
*** 74,80 ****
The value specifies a (%-encoded) URL relative path to the CGI script.
If the path does not begin with a (/), then it is taken to be relative to
the current document. The document referenced by this path is invoked
! as a CGI script, even if the server would not normally recognise it as
such. However, the directory containing the script must be enabled for
CGI scripts (with <A HREF="mod_alias.html#scriptalias">ScriptAlias</A>
or the ExecCGI <A HREF="core.html#options">Option</A>).<p>
--- 74,80 ----
The value specifies a (%-encoded) URL relative path to the CGI script.
If the path does not begin with a (/), then it is taken to be relative to
the current document. The document referenced by this path is invoked
! as a CGI script, even if the server would not normally recognize it as
such. However, the directory containing the script must be enabled for
CGI scripts (with <A HREF="mod_alias.html#scriptalias">ScriptAlias</A>
or the ExecCGI <A HREF="core.html#options">Option</A>).<p>
***************
*** 244,250 ****
<P> Anything that's not recognized as a variable or an operator is
treated as a string. Strings can also be quoted: <I>'string'</I>.
Unquoted strings can't contain whitespace (blanks and tabs)
! because it is used to seperate tokens such as variables. If
multiple strings are found in a row, they are concatenated using
blanks. So,
--- 244,250 ----
<P> Anything that's not recognized as a variable or an operator is
treated as a string. Strings can also be quoted: <I>'string'</I>.
Unquoted strings can't contain whitespace (blanks and tabs)
! because it is used to separate tokens such as variables. If
multiple strings are found in a row, they are concatenated using
blanks. So,
1.6 +1 -1 apache/htdocs/manual/mod/mod_log_config.html
Index: mod_log_config.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_log_config.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -C3 -r1.5 -r1.6
*** mod_log_config.html 1996/11/28 07:42:17 1.5
--- mod_log_config.html 1996/12/02 18:14:08 1.6
***************
*** 45,51 ****
Unless told otherwise with <tt>LogFormat</tt> the log files created by
<tt>TransferLog</tt> will be in standard "Common Log Format"
(CLF). The contents of each line in a CLF file are explained
! below. Alternatively, the log file can be customised (and if multiple
log files are used, each can have a different format). Custom formats
are set with <code>LogFormat</code> and <code>CustomLog</code>.
--- 45,51 ----
Unless told otherwise with <tt>LogFormat</tt> the log files created by
<tt>TransferLog</tt> will be in standard "Common Log Format"
(CLF). The contents of each line in a CLF file are explained
! below. Alternatively, the log file can be customized (and if multiple
log files are used, each can have a different format). Custom formats
are set with <code>LogFormat</code> and <code>CustomLog</code>.
1.3 +1 -1 apache/htdocs/manual/mod/mod_mime.html
Index: mod_mime.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_mime.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_mime.html 1996/11/21 10:30:51 1.2
--- mod_mime.html 1996/12/02 18:14:09 1.3
***************
*** 65,71 ****
<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<br>
--- 65,71 ----
<h2><a name="addhandler">AddHandler</a></h2>
! <strong>Syntax:</strong> <AddHandler <em>handler-name
extension</em>><br>
<strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_mime<br>
1.4 +1 -1 apache/htdocs/manual/mod/mod_negotiation.html
Index: mod_negotiation.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_negotiation.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** mod_negotiation.html 1996/11/26 09:23:51 1.3
--- mod_negotiation.html 1996/12/02 18:14:10 1.4
***************
*** 39,45 ****
<dl>
<dt>Content-Encoding:
! <dd>The encoding of the file. Currently only two encodings are recognised
by http; <code>x-compress</code> for compressed files, and
<code>x-gzip</code>
for gzipped files.
<dt>Content-Language:
--- 39,45 ----
<dl>
<dt>Content-Encoding:
! <dd>The encoding of the file. Currently only two encodings are recognized
by http; <code>x-compress</code> for compressed files, and
<code>x-gzip</code>
for gzipped files.
<dt>Content-Language:
1.3 +1 -1 apache/htdocs/manual/mod/mod_proxy.html
Index: mod_proxy.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_proxy.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_proxy.html 1996/11/21 10:30:52 1.2
--- mod_proxy.html 1996/12/02 18:14:11 1.3
***************
*** 167,173 ****
expiry-period = time-since-last-modification * <factor>
</pre>
For example, if the document was last modified 10 hours ago, and
! <factor> is 0.1, then the expiry period wil be set to 10*0.1 = 1 hour.
<p>If the expiry-period would be longer than that set by CacheMaxExpire,
then the latter takes precedence.
--- 167,173 ----
expiry-period = time-since-last-modification * <factor>
</pre>
For example, if the document was last modified 10 hours ago, and
! <factor> is 0.1, then the expiry period will be set to 10*0.1 = 1
hour.
<p>If the expiry-period would be longer than that set by CacheMaxExpire,
then the latter takes precedence.
1.2 +7 -7 apache/htdocs/manual/mod/mod_rewrite.html
Index: mod_rewrite.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_rewrite.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_rewrite.html 1996/11/28 07:09:18 1.1
--- mod_rewrite.html 1996/12/02 18:14:11 1.2
***************
*** 35,41 ****
<p>
It operates on the full URLs (including the PATH_INFO part) both in
per-server context (httpd.conf) and per-dir context (.htaccess) and even
! can generate QUERY_STRING parts on result. The rewrittten result can lead
to internal sub-processing, external request redirection or to internal proxy
throughput.
</b>
<p>
--- 35,41 ----
<p>
It operates on the full URLs (including the PATH_INFO part) both in
per-server context (httpd.conf) and per-dir context (.htaccess) and even
! can generate QUERY_STRING parts on result. The rewritten result can lead
to internal sub-processing, external request redirection or to internal proxy
throughput.
</b>
<p>
***************
*** 280,292 ****
<li><b>Program Format</b>
<p>
This is a Unix executable, not a lookup file. To create it you can use
! the language of your choice, but the result has to be a runable Unix
binary (i.e. either object-code or a script with the
magic cookie trick '<tt>#!/path/to/interpreter</tt>' as the first line).
<p>
This program gets started once at startup of the Apache servers and then
communicates with the rewriting engine over its <tt>stdin</tt> and
! <tt>stdout</tt> filehandles. For each map-function lookup it will
receive the key to lookup as a newline-terminated string on
<tt>stdin</tt>. It then has to give back the looked-up value as a
newline-terminated string on <tt>stdout</tt> or the four-character
string
--- 280,292 ----
<li><b>Program Format</b>
<p>
This is a Unix executable, not a lookup file. To create it you can use
! the language of your choice, but the result has to be a run-able Unix
binary (i.e. either object-code or a script with the
magic cookie trick '<tt>#!/path/to/interpreter</tt>' as the first line).
<p>
This program gets started once at startup of the Apache servers and then
communicates with the rewriting engine over its <tt>stdin</tt> and
! <tt>stdout</tt> file-handles. For each map-function lookup it will
receive the key to lookup as a newline-terminated string on
<tt>stdin</tt>. It then has to give back the looked-up value as a
newline-terminated string on <tt>stdout</tt> or the four-character
string
***************
*** 359,365 ****
When a substitution occurs for a new URL, this module has to
re-inject the URL into the server processing. To be able to do this it needs
to know what the corresponding URL-prefix or URL-base is. By default this
! prefix is the corresponding filepath itself. <b>But at most websites URLs
are
<b>NOT</b> directly related to physical filename paths, so this assumption
will be usually be wrong!</b> There you have to use the <tt>RewriteBase</tt>
directive to specify the correct URL-prefix.
--- 359,365 ----
When a substitution occurs for a new URL, this module has to
re-inject the URL into the server processing. To be able to do this it needs
to know what the corresponding URL-prefix or URL-base is. By default this
! prefix is the corresponding filepath itself. <b>But at most web-sites URLs
are
<b>NOT</b> directly related to physical filename paths, so this assumption
will be usually be wrong!</b> There you have to use the <tt>RewriteBase</tt>
directive to specify the correct URL-prefix.
***************
*** 367,373 ****
<p>
<table width=70% border=2 bgcolor="#c0c0e0" cellspacing=0 cellpadding=10>
<tr><td>
! So, if your webserver's URLs are <b>not</b> directly
related to physical file paths, you have to use <tt>RewriteBase</tt> in
every
<tt>.htaccess</tt> files where you want to use <tt>RewriteRule</tt>
directives.
--- 367,373 ----
<p>
<table width=70% border=2 bgcolor="#c0c0e0" cellspacing=0 cellpadding=10>
<tr><td>
! So, if your web-server's URLs are <b>not</b> directly
related to physical file paths, you have to use <tt>RewriteBase</tt> in
every
<tt>.htaccess</tt> files where you want to use <tt>RewriteRule</tt>
directives.
***************
*** 647,653 ****
<b>Example:</b>
<blockquote>
! To rewrite the Homepage of a site according to the ``<tt>User-Agent:</tt>''
header of the request, you can use the following:
<blockquote><pre>
--- 647,653 ----
<b>Example:</b>
<blockquote>
! To rewrite the Home-page of a site according to the ``<tt>User-Agent:</tt>''
header of the request, you can use the following:
<blockquote><pre>
***************
*** 818,824 ****
be handled by the Apache proxy module. If not you get an error from
the proxy module. Use this flag to achieve a more powerful
implementation
of the <tt>mod_proxy</tt> directive <tt>ProxyPass</tt>, to map
! some remote stuff into the namespace of the local server.
<p>
<li>'<strong><code>last|L</code></strong>' (<b>l</b>ast rule)<br>
Stop the rewriting process here and
--- 818,824 ----
be handled by the Apache proxy module. If not you get an error from
the proxy module. Use this flag to achieve a more powerful
implementation
of the <tt>mod_proxy</tt> directive <tt>ProxyPass</tt>, to map
! some remote stuff into the name-space of the local server.
<p>
<li>'<strong><code>last|L</code></strong>' (<b>l</b>ast rule)<br>
Stop the rewriting process here and
1.4 +4 -4 apache/htdocs/manual/mod/mod_usertrack.html
Index: mod_usertrack.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_usertrack.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** mod_usertrack.html 1996/11/28 07:42:17 1.3
--- mod_usertrack.html 1996/12/02 18:14:12 1.4
***************
*** 23,29 ****
Previously, the cookies module (now the user tracking module) did its
own logging, using the <tt>CookieLog</tt> directive. In this release,
this module does no logging at all. Instead, a configurable log
! format file should be used to log user clickstreams. This is possible
because the logging module now allows <a
href="multilogs.html">multiple log files</a>. The cookie itself is
logged by using the text <tt>%{cookie}n </tt>
--- 23,29 ----
Previously, the cookies module (now the user tracking module) did its
own logging, using the <tt>CookieLog</tt> directive. In this release,
this module does no logging at all. Instead, a configurable log
! format file should be used to log user click-streams. This is possible
because the logging module now allows <a
href="multilogs.html">multiple log files</a>. The cookie itself is
logged by using the text <tt>%{cookie}n </tt>
***************
*** 47,53 ****
<hr>
<a name="cookieexpires"><h2>CookieEnable</h2></A>
! <strong>Sytnax:</strong> CookieEnable <em>on | off</em><br>
<strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
<strong>Override:</strong> FileInfo<br>
--- 47,53 ----
<hr>
<a name="cookieexpires"><h2>CookieEnable</h2></A>
! <strong>Syntax:</strong> CookieEnable <em>on | off</em><br>
<strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
<strong>Override:</strong> FileInfo<br>
***************
*** 60,66 ****
per-directory basis.
<a name="cookieexpires"><h2>CookieExpires</h2></A>
! <strong>Sytnax:</strong> CookieExpires <em>expiry-period</em><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> optional<br>
<strong>Module:</strong> mod_usertrack<p>
--- 60,66 ----
per-directory basis.
<a name="cookieexpires"><h2>CookieExpires</h2></A>
! <strong>Syntax:</strong> CookieExpires <em>expiry-period</em><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> optional<br>
<strong>Module:</strong> mod_usertrack<p>
***************
*** 69,75 ****
this directive sets an expiry time on the cookie generated by the
usertrack module. The <i>expiry-period</i> can be given either as a
number of seconds, or in the format such as "2 weeks 3 days 7 hours".
! Valid denominations are: years, months, weeks, hours, minues and
seconds.
--- 69,75 ----
this directive sets an expiry time on the cookie generated by the
usertrack module. The <i>expiry-period</i> can be given either as a
number of seconds, or in the format such as "2 weeks 3 days 7 hours".
! Valid denominations are: years, months, weeks, hours, minutes and
seconds.
