Binding- Apache HTTP Server

From 83db25d47aa8e947264ce16db632fd619b64ae79 Mon Sep 17 00:00:00 2001 From: Yoshiki Hayashi Date: Wed, 31 Jul 2002 05:46:03 +0000 Subject: [PATCH] Update transformations. Remove allmodules.html.en. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96252 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/bind.html.en | 34 +++++---- docs/manual/mod/allmodules.html.en | 53 ------------- docs/manual/mod/mod_rewrite.html.en | 113 +++++++++++++++++++++------- 3 files changed, 107 insertions(+), 93 deletions(-) delete mode 100644 docs/manual/mod/allmodules.html.en diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en index b7779bed89..ee5ff531ac 100644 --- a/docs/manual/bind.html.en +++ b/docs/manual/bind.html.en @@ -1,13 +1,13 @@ -Binding- Apache HTTP Server

Apache HTTP Server Version 2.0
Binding
+Binding - Apache HTTP Server
Apache HTTP Server Version 2.0
Binding

Configuring Apache to listen on specific addresses and ports.
-
Overview
Special IPv6 Considerations
How This Works With Virtual Hosts
Overview
+
Overview
Special IPv6 Considerations
How This Works With Virtual Hosts
See also
Virtual Hosts
DNS Issues
Overview
-
Related Modules

core,
mpm_common
Related Directives

VirtualHost
Listen
+
Related Modules

core
mpm_common
Related Directives

VirtualHost
Listen

When Apache starts, it binds to some port and address on @@ -18,10 +18,12 @@ Virtual Host feature which determines how Apache responds to different IP addresses, hostnames and ports.
-
The Listen directive tells the server to accept +
The Listen + directive tells the server to accept incoming requests only on the specified port or address-and-port combinations. If only a port number is - specified in the Listen directive, the server + specified in the Listen + directive, the server listens to the given port on all interfaces. If an IP address is given as well as a port, the server will listen on the given port and interface. Multiple Listen directives may be used to @@ -97,14 +99,18 @@
Listen does not implement Virtual Hosts. It only tells the main server what addresses and ports to listen to. If no - <VirtualHost> directives are used, the server will behave + <VirtualHost> + directives are used, the server will behave the same for all accepted requests. However, - <VirtualHost> can be used to specify a different behavior + <VirtualHost> + can be used to specify a different behavior for one or more of the addresses 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 + 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 + <VirtualHost> + is set for an address and port that the server is not listening to, it cannot be accessed.
-
Apache HTTP Server Version 2.0
\ No newline at end of file +

Apache HTTP Server Version 2.0

\ No newline at end of file diff --git a/docs/manual/mod/allmodules.html.en b/docs/manual/mod/allmodules.html.en deleted file mode 100644 index a33a8ed6d9..0000000000 --- a/docs/manual/mod/allmodules.html.en +++ /dev/null @@ -1,53 +0,0 @@ - - core.xml - mod_access.xml - mod_actions.xml - mod_alias.xml - mod_asis.xml - mod_auth.xml - mod_auth_anon.xml - mod_auth_dbm.xml - mod_auth_digest.xml - mod_autoindex.xml - mod_cache.xml - mod_cern_meta.xml - mod_cgi.xml - mod_cgid.xml - mod_charset_lite.xml - mod_dav.xml - mod_deflate.xml - mod_dir.xml - mod_echo.xml - mod_env.xml - mod_example.xml - mod_expires.xml - mod_ext_filter.xml - mod_file_cache.xml - mod_headers.xml - mod_imap.xml - mod_include.xml - mod_info.xml - mod_isapi.xml - mod_log_config.xml - mod_mime.xml - mod_mime_magic.xml - mod_negotiation.xml - mod_proxy.xml - mod_rewrite.xml - mod_setenvif.xml - mod_so.xml - mod_ssl.xml - mod_speling.xml - mod_status.xml - mod_suexec.xml - mod_unique_id.xml - mod_userdir.xml - mod_usertrack.xml - mod_vhost_alias.xml - mpm_common.xml - mpm_netware.xml - mpm_winnt.xml - perchild.xml - prefork.xml - worker.xml - \ No newline at end of file diff --git a/docs/manual/mod/mod_rewrite.html.en b/docs/manual/mod/mod_rewrite.html.en index 51a34e4fd9..ab163d2902 100644 --- a/docs/manual/mod/mod_rewrite.html.en +++ b/docs/manual/mod/mod_rewrite.html.en @@ -1,9 +1,13 @@ -mod_rewrite- Apache HTTP Server

Apache HTTP Server Version 2.0
Apache Module mod_rewrite
Description: Provides a rule-based rewriting engine to rewrite requested -URLs on the fly
Status: Extension
Module Identifier: rewrite_module
Compatibility: Available in Apache 1.3 and later
Summary
+mod_rewrite - Apache HTTP Server
Apache HTTP Server Version 2.0
Apache Module mod_rewrite
Description: + Provides a rule-based rewriting engine to rewrite requested +URLs on the fly
Status: + Extension
Module Identifier: + rewrite_module
Compatibility: + Available in Apache 1.3 and later
Summary

``The great thing about mod_rewrite is it gives you all the configurability and flexibility of Sendmail. @@ -160,10 +164,10 @@ URLs on the fly
Figure 1:The control flow through the rewriting ruleset
- +

As you can see, first the URL is matched against the Pattern of each rule. When it fails mod_rewrite immediately stops processing this rule and continues with the @@ -210,10 +214,10 @@ URLs on the fly
Figure 2: The back-reference flow through a rule.
- +

We know this was a crash course on mod_rewrite's internal processing. But you will benefit from this knowledge when reading the following documentation of the available @@ -254,7 +258,14 @@ SCRIPT_URI=http://en1.engelschall.com/u/rse/ practical solutions for URL-based problems. There you can find real-life rulesets and additional information about mod_rewrite.
-
RewriteBase Directive
Description: Sets the base URL for per-directory rewrites
Syntax: RewriteBase URL-path
Default: See usage for information.
Context: directory, .htaccess
Override: FileInfo
Status: Extension
Module: mod_rewrite
+
RewriteBase Directive
Description: + Sets the base URL for per-directory rewrites
Syntax: + RewriteBase URL-path
Default: + See usage for information.
Context: + directory, .htaccess
Override: + FileInfo
Status: + Extension
Module: + mod_rewrite

The RewriteBase directive explicitly sets the base URL for per-directory rewrites. As you will see below, RewriteRule @@ -335,9 +346,16 @@ Result: implementation is correct.

-
RewriteCond Directive
Description: Defines a condition under which rewriting will take place -
Syntax: RewriteCond - TestString CondPattern
Default: None
Context: server config, virtual host, directory, .htaccess
Override: FileInfo
Status: Extension
Module: mod_rewrite
+
RewriteCond Directive
Description: + Defines a condition under which rewriting will take place +
Syntax: + RewriteCond + TestString CondPattern
Default: + None
Context: + server config, virtual host, directory, .htaccess
Override: + FileInfo
Status: + Extension
Module: + mod_rewrite

The RewriteCond directive defines a rule condition. Precede a RewriteRule directive with one or more RewriteCond directives. The following @@ -730,7 +748,14 @@ RewriteRule ^/$ /homepage.std.html [L] tables, etc. If you use any other browser you get the standard homepage.
-
RewriteEngine Directive
Description: Enables or disables runtime rewriting engine
Syntax: RewriteEngine on|off
Default: RewriteEngine off
Context: server config, virtual host, directory, .htaccess
Override: FileInfo
Status: Extension
Module: mod_rewrite
+
RewriteEngine Directive
Description: + Enables or disables runtime rewriting engine
Syntax: + RewriteEngine on|off
Default: + RewriteEngine off
Context: + server config, virtual host, directory, .htaccess
Override: + FileInfo
Status: + Extension
Module: + mod_rewrite

The RewriteEngine directive enables or disables the runtime rewriting engine. If it is set to @@ -745,16 +770,27 @@ RewriteRule ^/$ /homepage.std.html [L] inherited. This means that you need to have a RewriteEngine on directive for each virtual host in which you wish to use it.
-
RewriteLock Directive
Description: Sets the name of the lock file used for RewriteMap -synchronization
Syntax: RewriteLock file-path
Default: None
Context: server config
Status: Extension
Module: mod_rewrite
+
RewriteLock Directive
Description: + Sets the name of the lock file used for RewriteMap +synchronization
Syntax: + RewriteLock file-path
Default: + None
Context: + server config
Status: + Extension
Module: + mod_rewrite

This directive sets the filename for a synchronization lockfile which mod_rewrite needs to communicate with RewriteMap programs. Set this lockfile to a local path (not on a NFS-mounted device) when you want to use a rewriting map-program. It is not required for other types of rewriting maps.
-
RewriteLog Directive
Description: Sets the name of the file used for logging rewrite engine -processing
Syntax: RewriteLog file-path
Context: server config, virtual host
Status: Extension
Module: mod_rewrite
+
RewriteLog Directive
Description: + Sets the name of the file used for logging rewrite engine +processing
Syntax: + RewriteLog file-path
Context: + server config, virtual host
Status: + Extension
Module: + mod_rewrite

The RewriteLog directive sets the name of the file to which the server logs any rewriting actions it performs. If the name does not begin with a slash @@ -785,8 +821,14 @@ the user that starts the server. RewriteLog "/usr/local/var/apache/logs/rewrite.log" -
RewriteLogLevel Directive
Description: Sets the verbosity of the log file used by the rewrite -engine
Syntax: RewriteLogLevel Level
Default: RerwiteLogLevel 0
Context: server config, virtual host
Status: Extension
Module: mod_rewrite
+
RewriteLogLevel Directive
Description: + Sets the verbosity of the log file used by the rewrite +engine
Syntax: + RewriteLogLevel Level
Default: + RerwiteLogLevel 0
Context: + server config, virtual host
Status: + Extension
Module: + mod_rewrite

The RewriteLogLevel directive sets the verbosity level of the rewriting logfile. The default level 0 means no logging, while 9 or more means that practically all @@ -806,8 +848,14 @@ engine -
RewriteMap Directive
Description: Defines a mapping function for key-lookup
Syntax: RewriteMap MapName MapType:MapSource -
Default: None
Context: server config, virtual host
Status: Extension
Module: mod_rewrite
+
RewriteMap Directive
Description: + Defines a mapping function for key-lookup
Syntax: + RewriteMap MapName MapType:MapSource +
Default: + None
Context: + server config, virtual host
Status: + Extension
Module: + mod_rewrite

The RewriteMap directive defines a Rewriting Map which can be used inside rule substitution strings by the mapping-functions to @@ -1039,7 +1087,13 @@ request. This is no problem, because the external lookup only happens once! -
RewriteOptions Directive
Description: Sets some special options for the rewrite engine
Syntax: RewriteOptions Options
Default: None
Context: server config, virtual host, directory, .htaccess
Status: Extension
Module: mod_rewrite
+
RewriteOptions Directive
Description: + Sets some special options for the rewrite engine
Syntax: + RewriteOptions Options
Default: + None
Context: + server config, virtual host, directory, .htaccess
Status: + Extension
Module: + mod_rewrite

The RewriteOptions directive sets some special options for the current per-server or per-directory @@ -1055,8 +1109,15 @@ once! that conditions and rules of the parent directory's .htaccess configuration are inherited. -
RewriteRule Directive
Description: Defines rules for the rewriting engine
Syntax: RewriteRule - Pattern Substitution
Default: None
Context: server config, virtual host, directory, .htaccess
Override: FileInfo
Status: Extension
Module: mod_rewrite
+
RewriteRule Directive
Description: + Defines rules for the rewriting engine
Syntax: + RewriteRule + Pattern Substitution
Default: + None
Context: + server config, virtual host, directory, .htaccess
Override: + FileInfo
Status: + Extension
Module: + mod_rewrite

The RewriteRule directive is the real rewriting workhorse. The directive can occur more than once. Each directive then defines one single rewriting rule. The -- 2.40.0