diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en index a7f6b0e510..2e30b9e032 100644 --- a/docs/manual/bind.html.en +++ b/docs/manual/bind.html.en @@ -6,37 +6,37 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Binding - Apache HTTP Server - - - - + + + +
-

Modules | Directives | FAQ | Glossary | Sitemap

+

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.3

-
-
<-
+ +
<-
-Apache > HTTP Server > Documentation > Version 2.3

Binding

+Apache > HTTP Server > Documentation > Version 2.3

Binding

-

Available Languages:  de  | - en  | - fr  | - ja  | - ko 

+

Available Languages:  de  | + en  | + fr  | + ja  | + ko 

Configuring Apache to listen on specific addresses and ports.

-
top

Special IPv6 Considerations

A growing number of platforms implement IPv6, and - APR supports IPv6 on most of these platforms, + APR supports IPv6 on most of these platforms, allowing Apache to allocate IPv6 sockets, and to handle requests sent over IPv6.

@@ -99,14 +99,14 @@ platforms, but are disallowed by default on FreeBSD, NetBSD, and OpenBSD, in order to match the system-wide policy on those platforms. On systems where it is disallowed by default, a - special configure parameter can change this behavior + special configure parameter can change this behavior for Apache.

On the other hand, on some platforms, such as Linux and Tru64, the only way to handle both IPv6 and IPv4 is to use mapped addresses. If you want Apache to handle IPv4 and IPv6 connections with a minimum of sockets, which requires using IPv4-mapped IPv6 - addresses, specify the --enable-v4-mapped configure option.

+ addresses, specify the --enable-v4-mapped configure option.

--enable-v4-mapped is the default on all platforms except FreeBSD, NetBSD, and OpenBSD, so this is probably how your Apache was @@ -114,7 +114,7 @@

If you want Apache to handle IPv4 connections only, regardless of what your platform and APR will support, specify an IPv4 address on all - Listen directives, as in the + Listen directives, as in the following examples:

@@ -124,38 +124,38 @@

If your platform supports it and you want Apache to handle IPv4 and IPv6 connections on separate sockets (i.e., to disable IPv4-mapped - addresses), specify the --disable-v4-mapped configure option. --disable-v4-mapped is the + addresses), specify the --disable-v4-mapped configure option. --disable-v4-mapped is the default on FreeBSD, NetBSD, and OpenBSD.

-
top
+
top

How This Works With Virtual Hosts

-

The Listen directive does not implement +

The Listen directive does not implement Virtual Hosts - it only tells the main server what addresses and ports to listen on. If no - <VirtualHost> + <VirtualHost> directives are used, the server will behave in the same way for all accepted requests. However, - <VirtualHost> + <VirtualHost> can be used to specify a different behavior for one or more of the addresses or 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 + <VirtualHost> section should be created for the specified address and port to set the behavior of this virtual host. Note that if the - <VirtualHost> + <VirtualHost> is set for an address and port that the server is not listening to, it cannot be accessed.

-

Available Languages:  de  | - en  | - fr  | - ja  | - ko 

+

Available Languages:  de  | + en  | + fr  | + ja  | + ko 

+

Modules | Directives | FAQ | Glossary | Sitemap

\ No newline at end of file diff --git a/docs/manual/bind.xml.meta b/docs/manual/bind.xml.meta index 394eeb7013..ce6d33b256 100644 --- a/docs/manual/bind.xml.meta +++ b/docs/manual/bind.xml.meta @@ -2,8 +2,8 @@ bind - /./ - .. + / + . de diff --git a/docs/manual/caching.html.en b/docs/manual/caching.html.en index 993ce34760..8ccd5ad5da 100644 --- a/docs/manual/caching.html.en +++ b/docs/manual/caching.html.en @@ -6,68 +6,68 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Caching Guide - Apache HTTP Server - - - - + + + +
-

Modules | Directives | FAQ | Glossary | Sitemap

+

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.3

-
-
<-
+ +
<-

Caching Guide

-

Available Languages:  en 

+

Available Languages:  en 

-

This document supplements the mod_cache, - mod_disk_cache, mod_mem_cache, - mod_file_cache and htcacheclean reference documentation. +

This document supplements the mod_cache, + mod_disk_cache, mod_mem_cache, + mod_file_cache and htcacheclean reference documentation. It describes how to use Apache's caching features to accelerate web and proxy serving, while avoiding common problems and misconfigurations.

-
top

Caching Overview

-
Related ModulesRelated Directives
+
Related ModulesRelated Directives
-

There are two main stages in mod_cache that can - occur in the lifetime of a request. First, mod_cache +

There are two main stages in mod_cache that can + occur in the lifetime of a request. First, mod_cache is a URL mapping module, which means that if a URL has been cached, and the cached version of that URL has not expired, the request will - be served directly by mod_cache.

+ be served directly by mod_cache.

This means that any other stages that might ordinarily happen in the process of serving a request -- for example being handled - by mod_proxy, or mod_rewrite -- + by mod_proxy, or mod_rewrite -- won't happen. But then this is the point of caching content in the first place.

-

If the URL is not found within the cache, mod_cache +

If the URL is not found within the cache, mod_cache will add a filter to the request handling. After Apache has located the content by the usual means, the filter will be run as the content is served. If the content is determined to be cacheable, the content will be saved to the cache for future serving.

If the URL is found within the cache, but also found to have expired, - the filter is added anyway, but mod_cache will create + the filter is added anyway, but mod_cache will create a conditional request to the backend, to determine if the cached version is still current. If the cached version is still current, its meta-information will be updated and the request will be served from the @@ -114,7 +114,7 @@

When caching locally generated content, ensuring that - UseCanonicalName is set to + UseCanonicalName is set to On can dramatically improve the ratio of cache hits. This is because the hostname of the virtual-host serving the content forms a part of the cache key. With the setting set to On @@ -144,19 +144,19 @@

The default expiry period for cached entities is one hour, however - this can be easily over-ridden by using the CacheDefaultExpire directive. This + this can be easily over-ridden by using the CacheDefaultExpire directive. This default is only used when the original source of the content does not specify an expire time or time of last modification.

If a response does not include an Expires header but does - include a Last-Modified header, mod_cache - can infer an expiry period based on the use of the CacheLastModifiedFactor directive.

+ include a Last-Modified header, mod_cache + can infer an expiry period based on the use of the CacheLastModifiedFactor directive.

-

For local content, mod_expires may be used to +

For local content, mod_expires may be used to fine-tune the expiry period.

The maximum expiry period may also be controlled by using the - CacheMaxExpire.

+ CacheMaxExpire.

@@ -204,19 +204,19 @@

As mentioned already, the two styles of caching in Apache work - differently, mod_file_cache caching maintains file + differently, mod_file_cache caching maintains file contents as they were when Apache was started. When a request is made for a file that is cached by this module, it is intercepted and the cached file is served.

-

mod_cache caching on the other hand is more +

mod_cache caching on the other hand is more complex. When serving a request, if it has not been cached previously, the caching module will determine if the content is cacheable. The conditions for determining cachability of a response are;

    -
  1. Caching must be enabled for this URL. See the CacheEnable and CacheDisable directives.
    2. +
  2. Caching must be enabled for this URL. See the CacheEnable and CacheDisable directives.
  3. The response must have a HTTP status code of 200, 203, 300, 301 or 410.
    4. @@ -237,17 +237,17 @@
  4. If the response has a status of 200 (OK), the response must also include at least one of the "Etag", "Last-Modified" or the "Expires" headers, unless the - CacheIgnoreNoLastMod + CacheIgnoreNoLastMod directive has been used to require otherwise.
  5. If the response includes the "private" option in a "Cache-Control:" header, it will not be stored unless the - CacheStorePrivate has been + CacheStorePrivate has been used to require otherwise.
  6. Likewise, if the response includes the "no-store" option in a "Cache-Control:" header, it will not be stored unless the - CacheStoreNoStore has been + CacheStoreNoStore has been used.
  7. A response will not be stored if it includes a "Vary:" header @@ -275,9 +275,9 @@

    If a response with a "Vary" header is received by - mod_cache when requesting content by the backend it + mod_cache when requesting content by the backend it will attempt to handle it intelligently. If possible, - mod_cache will detect the headers attributed in the + mod_cache will detect the headers attributed in the "Vary" response in future requests and serve the correct cached response.

    @@ -287,12 +287,12 @@ Vary: negotiate,accept-language,accept-charset

-

mod_cache will only serve the cached content to +

mod_cache will only serve the cached content to requesters with matching accept-language and accept-charset headers matching those of the original request.

-
top
+
top

Security Considerations

@@ -300,7 +300,7 @@ Vary: negotiate,accept-language,accept-charset

Authentication, Authorization and Access Control

-

Using mod_cache is very much like having a built +

Using mod_cache is very much like having a built in reverse-proxy. Requests will be served by the caching module unless it determines that the backend should be queried. When caching local resources, this drastically changes the security model of Apache.

@@ -308,16 +308,16 @@ Vary: negotiate,accept-language,accept-charset

As traversing a filesystem hierarchy to examine potential .htaccess files would be a very expensive operation, partially defeating the point of caching (to speed up requests), - mod_cache makes no decision about whether a cached + mod_cache makes no decision about whether a cached entity is authorised for serving. In other words; if - mod_cache has cached some content, it will be served + mod_cache has cached some content, it will be served from the cache as long as that content has not expired.

If, for example, your configuration permits access to a resource by IP address you should ensure that this content is not cached. You can do this - by using the CacheDisable - directive, or mod_expires. Left unchecked, - mod_cache - very much like a reverse proxy - would cache + by using the CacheDisable + directive, or mod_expires. Left unchecked, + mod_cache - very much like a reverse proxy - would cache the content when served and then serve it to any client, on any IP address.

@@ -334,12 +334,12 @@ Vary: negotiate,accept-language,accept-charset

If the Apache user is compromised, for example through a flaw in a CGI process, it is possible that the cache may be targeted. When - using mod_disk_cache, it is relatively easy to + using mod_disk_cache, it is relatively easy to insert or modify a cached entity.

This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are - using mod_disk_cache you should bear this in mind - + using mod_disk_cache you should bear this in mind - ensure you upgrade Apache when security upgrades are announced and run CGI processes as a non-Apache user using suEXEC if possible.

@@ -366,12 +366,12 @@ Vary: negotiate,accept-language,accept-charset webserver such that the attacker can entirely control the content retrieved by the proxy.

-
top
+
top

File-Handle Caching

-
Related ModulesRelated Directives
+
Related ModulesRelated Directives

The act of opening a file can itself be a source of delay, particularly on network filesystems. By maintaining a cache of open file descriptors @@ -382,14 +382,14 @@ Vary: negotiate,accept-language,accept-charset

The most basic form of caching present in Apache is the file-handle - caching provided by mod_file_cache. Rather than caching + caching provided by mod_file_cache. Rather than caching file-contents, this cache maintains a table of open file descriptors. Files to be cached in this manner are specified in the configuration file using - the CacheFile + the CacheFile directive.

The - CacheFile directive + CacheFile directive instructs Apache to open the file when Apache is started and to re-use this file-handle for all subsequent access to this file.

@@ -399,7 +399,7 @@ Vary: negotiate,accept-language,accept-charset must ensure that your operating system's limit for the number of open files is set appropriately.

-

Although using CacheFile +

Although using CacheFile does not cause the file-contents to be cached per-se, it does mean that if the file changes while Apache is running these changes will not be picked up. The file will be consistently served as it was @@ -416,22 +416,22 @@ Vary: negotiate,accept-language,accept-charset

CacheEnable fd

-

mod_mem_cache also provides its own file-handle +

mod_mem_cache also provides its own file-handle caching scheme, which can be enabled via the - CacheEnable directive.

+ CacheEnable directive.

CacheEnable fd /
-

As with all of mod_cache this type of file-handle +

As with all of mod_cache this type of file-handle caching is intelligent, and handles will not be maintained beyond the expiry time of the cached content.

-
top
+
top

In-Memory Caching

-
Related ModulesRelated Directives
+
Related ModulesRelated Directives

Serving directly from system memory is universally the fastest method of serving content. Reading files from a disk controller or, even worse, @@ -496,8 +496,8 @@ sys 0m0.000s

MMapStatic Caching

-

mod_file_cache provides the - MMapStatic directive, which +

mod_file_cache provides the + MMapStatic directive, which allows you to have Apache map a static file's contents into memory at start time (using the mmap system call). Apache will use the in-memory contents for all subsequent accesses to this file.

@@ -505,11 +505,11 @@ sys 0m0.000s 
MMapStatic /usr/local/apache2/htdocs/index.html

As with the - CacheFile directive, any + CacheFile directive, any changes in these files will not be picked up by Apache after it has started.

-

The MMapStatic +

The MMapStatic directive does not keep track of how much memory it allocates, so you must ensure not to over-use the directive. Each Apache child process will replicate this memory, so it is critically important @@ -520,10 +520,10 @@ sys 0m0.000s

mod_mem_cache Caching

-

mod_mem_cache provides a HTTP-aware intelligent +

mod_mem_cache provides a HTTP-aware intelligent in-memory cache. It also uses heap memory directly, which means that even if MMap is not supported on your system, - mod_mem_cache may still be able to perform caching.

+ mod_mem_cache may still be able to perform caching.

Caching of this type is enabled via;

@@ -534,15 +534,15 @@ CacheEnable mem / # Limit the size of the cache to 1 Megabyte MCacheSize 1024 -
top
+
top

Disk-based Caching

-
Related ModulesRelated Directives
+
Related ModulesRelated Directives
-

mod_disk_cache provides a disk-based caching mechanism - for mod_cache. As with mod_mem_cache +

mod_disk_cache provides a disk-based caching mechanism + for mod_cache. As with mod_mem_cache this cache is intelligent and content will be served from the cache only as long as it is considered valid.

@@ -563,7 +563,7 @@ CacheDirLength 1

Understanding the Cache-Store

-

To store items in the cache, mod_disk_cache creates +

To store items in the cache, mod_disk_cache creates a 22 character hash of the url being requested. Thie hash incorporates the hostname, protocol, port, path and any CGI arguments to the URL, to ensure that multiple URLs do not collide.

@@ -573,13 +573,13 @@ CacheDirLength 1 be hashed to xyTGxSMO2b68mBCykqkp1w. This hash is used as a prefix for the naming of the files specific to that url within the cache, however first it is split up into directories as per - the CacheDirLevels and - CacheDirLength + the CacheDirLevels and + CacheDirLength directives.

-

CacheDirLevels +

CacheDirLevels specifies how many levels of subdirectory there should be, and - CacheDirLength + CacheDirLength specifies how many characters should be in each directory. With the example settings given above, the hash would be turned into a filename prefix as @@ -589,15 +589,15 @@ CacheDirLength 1 subdirectories or files that may be in a particular directory, as most file-systems slow down as this number increases. With setting of "1" for - CacheDirLength + CacheDirLength there can at most be 64 subdirectories at any particular level. With a setting of 2 there can be 64 * 64 subdirectories, and so on. Unless you have a good reason not to, using a setting of "1" - for CacheDirLength + for CacheDirLength is recommended.

Setting - CacheDirLevels + CacheDirLevels depends on how many files you anticipate to store in the cache. With the setting of "2" used in the above example, a grand total of 4096 subdirectories can ultimately be created. With @@ -618,7 +618,7 @@ CacheDirLength 1

Maintaining the Disk Cache

-

Although mod_disk_cache will remove cached content +

Although mod_disk_cache will remove cached content as it is expired, it does not maintain any information on the total size of the cache or how little free space may be left.

@@ -640,7 +640,7 @@ CacheDirLength 1 Figure 1: Typical cache growth / clean sequence.

-

Because mod_disk_cache does not itself pay attention +

Because mod_disk_cache does not itself pay attention to how much space is used you should ensure that htcacheclean is configured to leave enough "grow room" following a clean.

@@ -648,8 +648,8 @@ CacheDirLength 1
-

Available Languages:  en 

+

Available Languages:  en 

+

Modules | Directives | FAQ | Glossary | Sitemap

\ No newline at end of file diff --git a/docs/manual/caching.xml.meta b/docs/manual/caching.xml.meta index d50f9c467e..3254ec360c 100644 --- a/docs/manual/caching.xml.meta +++ b/docs/manual/caching.xml.meta @@ -2,8 +2,8 @@ caching - /./ - .. + / + . en diff --git a/docs/manual/configuring.html.en b/docs/manual/configuring.html.en index 5a77bfe055..7e311dbde8 100644 --- a/docs/manual/configuring.html.en +++ b/docs/manual/configuring.html.en @@ -6,54 +6,54 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Configuration Files - Apache HTTP Server - - - - + + + +
-

Modules | Directives | FAQ | Glossary | Sitemap

+

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.3

-
-
<-
+ +
<-

Configuration Files

+Apache > HTTP Server > Documentation > Version 2.3

Configuration Files

-

Available Languages:  de  | - en  | - ja  | - ko 

+

Available Languages:  de  | + en  | + ja  | + ko 

This document describes the files used to configure the Apache HTTP server.

-
top

Syntax of the Configuration Files

@@ -76,12 +76,12 @@ HTTP server.

without starting the server by using apachectl configtest or the -t command line option.

-
top
+
top

Modules

-
Related ModulesRelated Directives
+
Related ModulesRelated Directives

Apache is a modular server. This implies that only the most basic functionality is included in the core server. Extended @@ -90,25 +90,25 @@ HTTP server.

included in the server at compile-time. If the server is compiled to use dynamically loaded modules, then modules can be compiled separately and added at - any time using the LoadModule + any time using the LoadModule directive. Otherwise, Apache must be recompiled to add or remove modules. Configuration directives may be included conditional on a - presence of a particular module by enclosing them in an <IfModule> block.

+ presence of a particular module by enclosing them in an <IfModule> block.

To see which modules are currently compiled into the server, you can use the -l command line option.

-
top
+
top

Scope of Directives

-
Related ModulesRelated Directives
+
Related ModulesRelated Directives

Directives placed in the main configuration files apply to the entire server. If you wish to change the configuration for only a part of the server, you can scope your directives by - placing them in <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, and <LocationMatch> + placing them in <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, and <LocationMatch> sections. These sections limit the application of the directives which they enclose to particular filesystem locations or URLs. They can also be nested, allowing for very @@ -117,7 +117,7 @@ HTTP server.

Apache has the capability to serve many different websites simultaneously. This is called Virtual Hosting. Directives can also be scoped by placing them - inside <VirtualHost> + inside <VirtualHost> sections, so that they will only apply to requests for a particular website.

@@ -128,17 +128,17 @@ HTTP server.

can be placed in which sections, check the Context of the directive. For further information, we provide details on How Directory, Location and Files sections work.

-
top
+
top

.htaccess Files

-
Related ModulesRelated Directives
+
Related ModulesRelated Directives

Apache allows for decentralized management of configuration via special files placed inside the web tree. The special files are usually called .htaccess, but any name can be - specified in the AccessFileName + specified in the AccessFileName directive. Directives placed in .htaccess files apply to the directory where you place the file, and all sub-directories. The .htaccess files follow the @@ -150,18 +150,18 @@ HTTP server.

.htaccess files, check the Context of the directive. The server administrator further controls what directives may be placed in .htaccess files by - configuring the AllowOverride + configuring the AllowOverride directive in the main configuration files.

For more information on .htaccess files, see the .htaccess tutorial.

-

Available Languages:  de  | - en  | - ja  | - ko 

+

Available Languages:  de  | + en  | + ja  | + ko 

+

Modules | Directives | FAQ | Glossary | Sitemap

\ No newline at end of file diff --git a/docs/manual/configuring.xml.meta b/docs/manual/configuring.xml.meta index 9a6552e81f..201286fae5 100644 --- a/docs/manual/configuring.xml.meta +++ b/docs/manual/configuring.xml.meta @@ -2,8 +2,8 @@ configuring - /./ - .. + / + . de diff --git a/docs/manual/content-negotiation.html.en b/docs/manual/content-negotiation.html.en index d5380ae400..509d25b533 100644 --- a/docs/manual/content-negotiation.html.en +++ b/docs/manual/content-negotiation.html.en @@ -6,21 +6,21 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Content Negotiation - Apache HTTP Server - - - - + + + +
-

Modules | Directives | FAQ | Glossary | Sitemap

+

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.3

-
-
<-
+ +
<-

Content Negotiation

+Apache > HTTP Server > Documentation > Version 2.3

Content Negotiation

-

Available Languages:  en  | - ja  | - ko 

+

Available Languages:  en  | + ja  | + ko 

@@ -33,21 +33,21 @@ incomplete negotiation information.

Content negotiation is provided by the - mod_negotiation module, which is compiled in + mod_negotiation module, which is compiled in by default.

-
top
+
top

Negotiation in Apache

@@ -124,7 +124,7 @@ Negotiation

A type map is a document which is associated with the handler named type-map (or, for backwards-compatibility with - older Apache configurations, the MIME-type + older Apache configurations, the MIME-type application/x-type-map). Note that to use this feature, you must have a handler set in the configuration that defines a file suffix as type-map; this is best done @@ -196,9 +196,9 @@ Negotiation

Multiviews

MultiViews is a per-directory option, meaning it - can be set with an Options - directive within a <Directory>, <Location> or <Files> section in - httpd.conf, or (if AllowOverride is properly set) in + can be set with an Options + directive within a <Directory>, <Location> or <Files> section in + httpd.conf, or (if AllowOverride is properly set) in .htaccess files. Note that Options All does not set MultiViews; you have to ask for it by name.

@@ -214,7 +214,7 @@ Negotiation then chooses the best match to the client's requirements.

MultiViews may also apply to searches for the file - named by the DirectoryIndex directive, if the + named by the DirectoryIndex directive, if the server is trying to index a directory. If the configuration files specify

DirectoryIndex index

@@ -226,11 +226,11 @@ Negotiation

If one of the files found when reading the directory does not have an extension recognized by mod_mime to designate its Charset, Content-Type, Language, or Encoding, then the result - depends on the setting of the MultiViewsMatch directive. This + depends on the setting of the MultiViewsMatch directive. This directive determines whether handlers, filters, and other extension types can participate in MultiViews negotiation.

-
top
+
top

The Negotiation Methods

@@ -396,7 +396,7 @@ Negotiation indicate the dimensions of variance. -
top
+
top

Fiddling with Quality Values

@@ -464,10 +464,10 @@ Negotiation these error messages, it is possible to configure Apache to ignore the Accept-language in these cases and provide a document that does not explicitly match the client's request. The - ForceLanguagePriority + ForceLanguagePriority directive can be used to override one or both of these error messages and substitute the servers judgement in the form of the - LanguagePriority + LanguagePriority directive.

The server will also attempt to match language-subsets when no @@ -482,7 +482,7 @@ Negotiation English in general. Unfortunately, many current clients have default configurations that resemble this.) However, if no other language match is possible and the server is about to return a "No - Acceptable Variants" error or fallback to the LanguagePriority, the server + Acceptable Variants" error or fallback to the LanguagePriority, the server will ignore the subset specification and match en-GB against en documents. Implicitly, Apache will add the parent language to the client's acceptable language list with @@ -495,10 +495,10 @@ Negotiation

In order to support advanced techniques (such as cookies or special URL-paths) to determine the user's preferred language, - since Apache 2.0.47 mod_negotiation recognizes + since Apache 2.0.47 mod_negotiation recognizes the environment variable prefer-language. If it exists and contains an - appropriate language tag, mod_negotiation will + appropriate language tag, mod_negotiation will try to select a matching variant. If there's no such variant, the normal negotiation process applies.

@@ -507,7 +507,7 @@ Negotiation Header append Vary cookie

-
top
+
top

Extensions to Transparent Content Negotiation

@@ -521,7 +521,7 @@ to use them as candidate variants whenever their encodings are acceptable according to the Accept-Encoding request header. The RVSA/1.0 implementation does not round computed quality factors to 5 decimal places before choosing the best variant.

-
top
+
top

Note on hyperlinks and naming conventions

@@ -631,7 +631,7 @@ factors to 5 decimal places before choosing the best variant.

extension (including an encoding extension if there is one) must be on the right hand side of the MIME-type extension (e.g., foo.html.en).

-
top
+
top

Note on Caching

@@ -647,7 +647,7 @@ factors to 5 decimal places before choosing the best variant.

responses.

For requests which come from a HTTP/1.0 compliant client - (either a browser or a cache), the directive CacheNegotiatedDocs can be + (either a browser or a cache), the directive CacheNegotiatedDocs can be used to allow caching of responses which were subject to negotiation. This directive can be given in the server config or virtual host, and takes no arguments. It has no effect on requests @@ -660,7 +660,7 @@ factors to 5 decimal places before choosing the best variant.

encourage a cache to use the local copy regardless of the negotiation dimensions, set the force-no-vary environment variable.

-
top
+
top

More Information

@@ -670,10 +670,10 @@ factors to 5 decimal places before choosing the best variant.

updated to include changes in Apache 2.0.

-

Available Languages:  en  | - ja  | - ko 

+

Available Languages:  en  | + ja  | + ko 

+

Modules | Directives | FAQ | Glossary | Sitemap

\ No newline at end of file diff --git a/docs/manual/content-negotiation.xml.meta b/docs/manual/content-negotiation.xml.meta index 5053c9d982..b8337db2e8 100644 --- a/docs/manual/content-negotiation.xml.meta +++ b/docs/manual/content-negotiation.xml.meta @@ -2,8 +2,8 @@ content-negotiation - /./ - .. + / + . en diff --git a/docs/manual/custom-error.html.en b/docs/manual/custom-error.html.en index b4f25362a6..cbf50c8502 100644 --- a/docs/manual/custom-error.html.en +++ b/docs/manual/custom-error.html.en @@ -6,22 +6,22 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Custom Error Responses - Apache HTTP Server - - - - + + + +
-

Modules | Directives | FAQ | Glossary | Sitemap

+

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.3

-
-
<-
+ +
<-

Custom Error Responses

+Apache > HTTP Server > Documentation > Version 2.3

Custom Error Responses

-

Available Languages:  en  | - es  | - ja  | - ko 

+

Available Languages:  en  | + es  | + ja  | + ko 

Additional functionality allows webmasters to configure the response @@ -34,11 +34,11 @@ then this response can be replaced with either some friendlier text or by a redirection to another URL (local or external).

-
top

Configuration

-

Use of ErrorDocument is enabled +

Use of ErrorDocument is enabled for .htaccess files when the - AllowOverride is set accordingly.

+ AllowOverride is set accordingly.

Here are some examples...

@@ -135,7 +135,7 @@
  • A local URL to redirect to.
    • -
    top
    +
    top

    Custom Error Responses and Redirects

    @@ -194,11 +194,11 @@
    -

    Available Languages:  en  | - es  | - ja  | - ko 

    +

    Available Languages:  en  | + es  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/custom-error.xml.meta b/docs/manual/custom-error.xml.meta index 098e0061d1..cd88703fca 100644 --- a/docs/manual/custom-error.xml.meta +++ b/docs/manual/custom-error.xml.meta @@ -2,8 +2,8 @@ custom-error - /./ - .. + / + . en diff --git a/docs/manual/dns-caveats.html.en b/docs/manual/dns-caveats.html.en index 1e2507baac..1816b1a0bb 100644 --- a/docs/manual/dns-caveats.html.en +++ b/docs/manual/dns-caveats.html.en @@ -6,21 +6,21 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Issues Regarding DNS and Apache - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Issues Regarding DNS and Apache

    +Apache > HTTP Server > Documentation > Version 2.3

    Issues Regarding DNS and Apache

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    This page could be summarized with the statement: don't @@ -31,13 +31,13 @@ or denial and theft of service attacks (including users able to steal hits from other users).

    -
    top
    +
    top

    Denial of Service

    @@ -142,16 +142,16 @@ this happens requires a more in-depth discussion of how Apache matches up incoming requests with the virtual host that will serve it. A rough document describing this is available.

    -
    top
    +
    top

    The "main server" Address

    The addition of name-based virtual host support in Apache 1.1 requires Apache to know - the IP address(es) of the host that httpd + the IP address(es) of the host that httpd is running on. To get this address it uses either the global - ServerName + ServerName (if present) or calls the C function gethostname (which should return the same as typing "hostname" at the command prompt). Then it performs a DNS lookup on this address. @@ -171,9 +171,9 @@ with the HOSTRESORDER environment variable set to "local". This all depends on what OS and resolver libraries you are using. It also affects CGIs unless you use - mod_env to control the environment. It's best + mod_env to control the environment. It's best to consult the man pages or FAQs for your OS.

    -
    top
    +
    top

    Tips to Avoid These Problems

    @@ -181,23 +181,23 @@ -
    top
    +
    top

    Appendix: Future Directions

    @@ -234,10 +234,10 @@ webservers.

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/dns-caveats.xml.meta b/docs/manual/dns-caveats.xml.meta index 5cb56123c9..a218acd9dd 100644 --- a/docs/manual/dns-caveats.xml.meta +++ b/docs/manual/dns-caveats.xml.meta @@ -2,8 +2,8 @@ dns-caveats - /./ - .. + / + . en diff --git a/docs/manual/dso.html.en b/docs/manual/dso.html.en index b44327462f..3aa0a1d947 100644 --- a/docs/manual/dso.html.en +++ b/docs/manual/dso.html.en @@ -6,77 +6,77 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Dynamic Shared Object (DSO) Support - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Dynamic Shared Object (DSO) Support

    +Apache > HTTP Server > Documentation > Version 2.3

    Dynamic Shared Object (DSO) Support

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    The Apache HTTP Server is a modular program where the administrator can choose the functionality to include in the server by selecting a set of modules. The modules can be - statically compiled into the httpd binary when the + statically compiled into the httpd binary when the server is built. Alternatively, modules can be compiled as Dynamic Shared Objects (DSOs) that exist separately from the - main httpd binary file. DSO modules may be + main httpd binary file. DSO modules may be compiled at the time the server is built, or they may be compiled and added at a later time using the Apache Extension - Tool (apxs).

    + Tool (apxs).

    This document describes how to use DSO modules as well as the theory behind their use.

    -
    • Implementation
      • -
    • Usage Summary
      • -
    • Background
      • -
    • Advantages and Disadvantages
      • + -
      top
      +
      top

      Implementation

      -
      Related ModulesRelated Directives
      +
      Related ModulesRelated Directives

      The DSO support for loading individual Apache modules is based - on a module named mod_so which must be statically + on a module named mod_so which must be statically compiled into the Apache core. It is the only module besides - core which cannot be put into a DSO + core which cannot be put into a DSO itself. Practically all other distributed Apache modules can then be placed into a DSO by individually enabling the DSO build for - them via configure's + them via configure's --enable-module=shared option as discussed in the install documentation. After a module is compiled into a DSO named mod_foo.so you - can use mod_so's LoadModule command in your + can use mod_so's LoadModule command in your httpd.conf file to load this module at server startup or restart.

      To simplify this creation of DSO files for Apache modules (especially for third-party modules) a new support program - named apxs (APache + named apxs (APache eXtenSion) is available. It can be used to build DSO based modules outside of the Apache source tree. The idea is - simple: When installing Apache the configure's + simple: When installing Apache the configure's make install procedure installs the Apache C header files and puts the platform-dependent compiler and - linker flags for building DSO files into the apxs - program. This way the user can use apxs to compile + linker flags for building DSO files into the apxs + program. This way the user can use apxs to compile his Apache module sources without the Apache distribution source tree and without having to fiddle with the platform-dependent compiler and linker flags for DSO support.

      -
      top
      +
    top

    Usage Summary

    @@ -123,7 +123,7 @@ $ make install Build and install a third-party Apache module, say mod_foo.c, into its own DSO mod_foo.so outside of the Apache - source tree using apxs: + source tree using apxs:

    $ cd /path/to/3rdparty
    @@ -134,10 +134,10 @@ $ apxs -i -a -n foo mod_foo.la

    In all cases, once the shared module is compiled, you must - use a LoadModule + use a LoadModule directive in httpd.conf to tell Apache to activate the module.

    -
    top
    +
    top

    Background

    @@ -239,7 +239,7 @@ $ apxs -i -a -n foo mod_foo.la modules into the Apache core functionality. So, Apache is really predestined for using DSO to load its modules at run-time.

    -
    top
    +
    top

    Advantages and Disadvantages

    @@ -249,9 +249,9 @@ $ apxs -i -a -n foo mod_foo.la
    • The server package is more flexible at run-time because the actual server process can be assembled at run-time via - LoadModule + LoadModule httpd.conf configuration commands instead of - configure options at build-time. For instance + configure options at build-time. For instance this way one is able to run different server instances (standard & SSL version, minimalistic & powered up version [mod_perl, PHP3], etc.) with only one Apache @@ -265,7 +265,7 @@ $ apxs -i -a -n foo mod_foo.la etc.
    • Easier Apache module prototyping because with the - DSO/apxs pair you can both work outside the + DSO/apxs pair you can both work outside the Apache source tree and only need an apxs -i command followed by an apachectl restart to bring a new version of your currently developed module into @@ -306,10 +306,10 @@ $ apxs -i -a -n foo mod_foo.la
    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/dso.xml.meta b/docs/manual/dso.xml.meta index 69a3c006c0..318174a753 100644 --- a/docs/manual/dso.xml.meta +++ b/docs/manual/dso.xml.meta @@ -2,8 +2,8 @@ dso - /./ - .. + / + . en diff --git a/docs/manual/env.html.en b/docs/manual/env.html.en index aa647aecc8..84c52e132e 100644 --- a/docs/manual/env.html.en +++ b/docs/manual/env.html.en @@ -6,21 +6,21 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Environment Variables in Apache - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Environment Variables in Apache

    +Apache > HTTP Server > Documentation > Version 2.3

    Environment Variables in Apache

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    The Apache HTTP Server provides a mechanism for storing @@ -43,24 +43,24 @@ manipulation mechanisms provided by your operating system shell.

    -
    -
    top
    +
    top

    Using Environment Variables

    -
    Related ModulesRelated Directives
    +
    Related ModulesRelated Directives

    CGI Scripts

    @@ -153,7 +153,7 @@

    Access to the server can be controlled based on the value of environment variables using the allow from env= and deny from env= directives. In combination with - SetEnvIf, this + SetEnvIf, this allows for flexible control of access to the server based on characteristics of the client. For example, you can use these directives to deny access to a particular browser (User-Agent). @@ -164,12 +164,12 @@

    Environment variables can be logged in the access log using - the LogFormat + the LogFormat option %e. In addition, the decision on whether or not to log requests can be made based on the status of environment variables using the conditional form of the - CustomLog - directive. In combination with SetEnvIf this allows for flexible control of which + CustomLog + directive. In combination with SetEnvIf this allows for flexible control of which requests are logged. For example, you can choose not to log requests for filenames ending in gif, or you can choose to only log requests from clients which are outside your @@ -179,7 +179,7 @@

    Conditional Response Headers

    -

    The Header +

    The Header directive can use the presence or absence of an environment variable to determine whether or not a certain HTTP header will be placed in the response to the @@ -192,8 +192,8 @@

    External Filter Activation

    -

    External filters configured by mod_ext_filter - using the ExtFilterDefine directive can +

    External filters configured by mod_ext_filter + using the ExtFilterDefine directive can by activated conditional on an environment variable using the disableenv= and enableenv= options.

    @@ -202,7 +202,7 @@

    The %{ENV:...} form of TestString in - the RewriteCond + the RewriteCond allows mod_rewrite's rewrite engine to make decisions conditional on environment variables. Note that the variables accessible in mod_rewrite without the @@ -210,7 +210,7 @@ variables. Rather, they are variables special to mod_rewrite which cannot be accessed from other modules.

    -
    top
    +
    top

    Special Purpose Environment Variables

    @@ -219,7 +219,7 @@ mechanisms to modify the way Apache behaves when talking to particular clients. To make these mechanisms as flexible as possible, they are invoked by defining environment variables, - typically with BrowserMatch, though SetEnv and PassEnv could also be used, for example.

    + typically with BrowserMatch, though SetEnv and PassEnv could also be used, for example.

    downgrade-1.0

    @@ -259,9 +259,9 @@

    When set to a value of "1", this variable disables the DEFLATE - output filter provided by mod_deflate for + output filter provided by mod_deflate for content-types other than text/html. If you'd rather - use statically compressed files; mod_negotiation + use statically compressed files; mod_negotiation evaluates the variable as well (not only for gzip, but for all encodings that differ from "identity").

    @@ -269,8 +269,8 @@

    no-gzip

    When set, the DEFLATE filter of - mod_deflate will be turned off and - mod_negotiation will refuse to deliver encoded + mod_deflate will be turned off and + mod_negotiation will refuse to deliver encoded resources.

    @@ -278,16 +278,16 @@

    nokeepalive

    -

    This disables KeepAlive +

    This disables KeepAlive when set.

    prefer-language

    -

    This influences mod_negotiation's behaviour. If +

    This influences mod_negotiation's behaviour. If it contains a language tag (such as en, ja - or x-klingon), mod_negotiation tries + or x-klingon), mod_negotiation tries to deliver a variant with that language. If there's no such variant, the normal negotiation process applies.

    @@ -329,11 +329,11 @@

    force-proxy-request-1.0, proxy-nokeepalive, proxy-sendchunked, proxy-sendcl

    These directives alter the protocol behavior of - mod_proxy. See the mod_proxy + mod_proxy. See the mod_proxy documentation for more details.

    -
    top
    +
    top

    Examples

    @@ -405,10 +405,10 @@ SetEnvIf Referer "^$" local_referal
    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/env.xml.meta b/docs/manual/env.xml.meta index a91b8e7911..fd4d4a5499 100644 --- a/docs/manual/env.xml.meta +++ b/docs/manual/env.xml.meta @@ -2,8 +2,8 @@ env - /./ - .. + / + . en diff --git a/docs/manual/filter.html.en b/docs/manual/filter.html.en index 7564287553..2686966353 100644 --- a/docs/manual/filter.html.en +++ b/docs/manual/filter.html.en @@ -6,36 +6,36 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Filters - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Filters

    -

    Available Languages:  en  | - es  | - fr  | - ja  | - ko 

    +

    Available Languages:  en  | + es  | + fr  | + ja  | + ko 

    This document describes the use of filters in Apache.

    -
    -
    top
    +
    top

    Smart Filtering

    Smart filtering applies different filter providers according to the state of request processing

    -

    mod_filter, included in Apache 2.1 and later, +

    mod_filter, included in Apache 2.1 and later, enables the filter chain to be configured dynamically at run time. So for example you can set up a proxy to rewrite HTML with an HTML filter and JPEG images with a completely @@ -95,7 +95,7 @@ compressible type and not already compressed

  • A charset conversion filter will be inserted if a text document is not already in the desired charset
    • -
    top
    +
    top

    Using Filters

    @@ -106,32 +106,32 @@ can be mixed freely with either simple or dynamic Output filtering).

    The Simple Way is the only way to configure input filters, and is sufficient for output filters where you need a static filter chain. Relevant directives are - SetInputFilter, - SetOutputFilter, - AddInputFilter, - AddOutputFilter, - RemoveInputFilter, and - RemoveOutputFilter.

    + SetInputFilter, + SetOutputFilter, + AddInputFilter, + AddOutputFilter, + RemoveInputFilter, and + RemoveOutputFilter.

    The Dynamic Way enables both static and flexible, dynamic configuration -of output filters, as discussed in the mod_filter page. +of output filters, as discussed in the mod_filter page. Relevant directives are - FilterChain, - FilterDeclare, and - FilterProvider.

    + FilterChain, + FilterDeclare, and + FilterProvider.

    -

    One further directive AddOutputFilterByType is still supported, +

    One further directive AddOutputFilterByType is still supported, but may be problematic and is now deprecated. Use dynamic configuration instead.

    -

    Available Languages:  en  | - es  | - fr  | - ja  | - ko 

    +

    Available Languages:  en  | + es  | + fr  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/filter.xml.meta b/docs/manual/filter.xml.meta index 84b1055b04..439dfd53c5 100644 --- a/docs/manual/filter.xml.meta +++ b/docs/manual/filter.xml.meta @@ -2,8 +2,8 @@ filter - /./ - .. + / + . en diff --git a/docs/manual/glossary.html.en b/docs/manual/glossary.html.en index 3ef2fd9b7f..9d50cb1991 100644 --- a/docs/manual/glossary.html.en +++ b/docs/manual/glossary.html.en @@ -6,29 +6,29 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Glossary - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Glossary

    -

    Available Languages:  de  | - en  | - es  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ko 

    This glossary defines some of the common terminology related to Apache in particular, and web serving in general. More information on each concept is provided in the links.

    -
    top
    +
    top

    Definitions

    @@ -48,10 +48,10 @@
    APache eXtension Tool (apxs)
    -
    A perl script that aids in compiling module sources into Dynamic Shared Objects - (DSOs) and helps install them in the +
    A perl script that aids in compiling module sources into Dynamic Shared Objects + (DSOs) and helps install them in the Apache Web server.
    - See: Manual Page: apxs + See: Manual Page: apxs
    Apache Portable Runtime (APR)
    @@ -72,8 +72,8 @@
    Certificate
    A data record used for authenticating network entities such as a server or a client. A certificate contains X.509 information pieces - about its owner (called the subject) and the signing Certification Authority (called - the issuer), plus the owner's public + about its owner (called the subject) and the signing Certification Authority (called + the issuer), plus the owner's public key and the signature made by the CA. Network entities verify these signatures using CA certificates.
    @@ -82,9 +82,9 @@
    Certificate Signing Request (CSR)
    -
    An unsigned certificate for - submission to a Certification - Authority, which signs it with the Private Key of their CA +
    An unsigned certificate for + submission to a Certification + Authority, which signs it with the Private Key of their CA Certificate. Once the CSR is signed, it becomes a real certificate.
    See: SSL/TLS Encryption @@ -106,8 +106,8 @@
    Ciphertext
    -
    The result after Plaintext is - passed through a Cipher.
    See: SSL/TLS Encryption +
    The result after Plaintext is + passed through a Cipher.
    See: SSL/TLS Encryption
    Common @@ -120,24 +120,24 @@
    Configuration Directive
    -
    See: Directive
    +
    See: Directive
    Configuration File
    -
    A text file containing Directives +
    A text file containing Directives that control the configuration of Apache.
    See: Configuration Files
    CONNECT
    -
    An HTTP method for proxying raw data +
    An HTTP method for proxying raw data channels over HTTP. It can be used to encapsulate other protocols, such as the SSL protocol.
    Context
    -
    An area in the configuration - files where certain types of directives are allowed.
    +
    An area in the configuration + files where certain types of directives are allowed.
    See: Terms Used to Describe Apache Directives
    @@ -145,7 +145,7 @@
    Digital Signature
    An encrypted text block that validates a certificate or other file. A - Certification Authority + Certification Authority creates a signature by generating a hash of the Public Key embedded in a Certificate, then encrypting the hash with its own Private Key. Only the CA's public key can decrypt the signature, @@ -156,14 +156,14 @@
    Directive
    A configuration command that controls one or more aspects of Apache's - behavior. Directives are placed in the Configuration File
    + behavior. Directives are placed in the Configuration File
    See: Directive Index
    Dynamic Shared Object (DSO)
    -
    Modules compiled separately from the - Apache httpd binary that can be loaded on-demand.
    +
    Modules compiled separately from the + Apache httpd binary that can be loaded on-demand.
    See: Dynamic Shared Object Support
    @@ -191,7 +191,7 @@ server. Input filters process data sent by the client to the server, while output filters process documents on the server before they are sent to the client. For example, the INCLUDES output filter - processes documents for Server Side + processes documents for Server Side Includes.
    See: Filters @@ -210,7 +210,7 @@ type. Normally, all files are simply served by the server, but certain file types are "handled" separately. For example, the cgi-script handler designates files to be processed as - CGIs.
    + CGIs.
    See: Apache's Handler Use @@ -221,21 +221,21 @@
    Header
    -
    The part of the HTTP request and +
    The part of the HTTP request and response that is sent before the actual content, and that contains meta-information describing the content.
    .htaccess
    -
    A configuration file that - is placed inside the web tree and applies configuration directives to the directory where it is +
    A configuration file that + is placed inside the web tree and applies configuration directives to the directory where it is placed and all sub-directories. Despite its name, this file can hold almost any type of directive, not just access-control directives.
    See: Configuration Files
    httpd.conf
    -
    The main Apache configuration +
    The main Apache configuration file. The default location is /usr/local/apache2/conf/httpd.conf, but it may be moved using run-time or compile-time configuration.
    @@ -252,12 +252,12 @@
    HTTPS
    The HyperText Transfer Protocol (Secure), the standard encrypted communication mechanism on the World Wide Web. This is actually just HTTP - over SSL.
    + over SSL.
    See: SSL/TLS Encryption
    Method
    -
    In the context of HTTP, an action to +
    In the context of HTTP, an action to perform on a resource, specified on the request line by the client. Some of the methods available in HTTP are GET, POST, and PUT. @@ -276,20 +276,20 @@ separated by a slash. Some examples are text/html, image/gif, and application/octet-stream. In HTTP, the MIME-type is transmitted in the Content-Type - header.
    + header.
    See: mod_mime
    Module
    An independent part of a program. Much of Apache's functionality is contained in modules that you can choose to include or exclude. Modules - that are compiled into the Apache httpd binary are + that are compiled into the Apache httpd binary are called static modules, while modules that are stored separately and can be optionally loaded at run-time are called - dynamic modules or DSOs. + dynamic modules or DSOs. Modules that are included by default are called base modules. Many modules are available for Apache - that are not distributed as part of the Apache HTTP Server tarball. These are referred to as + that are not distributed as part of the Apache HTTP Server tarball. These are referred to as third-party modules.
    See: Module Index
    @@ -313,7 +313,7 @@
    Pass Phrase
    The word or phrase that protects private key files. It prevents unauthorized users from encrypting them. Usually it's just the secret - encryption/decryption key used for Ciphers.
    + encryption/decryption key used for Ciphers.
    See: SSL/TLS Encryption
    @@ -321,7 +321,7 @@
    The unencrypted text.
    Private Key
    -
    The secret key in a Public Key +
    The secret key in a Public Key Cryptography system, used to decrypt incoming messages and sign outgoing ones.
    See: SSL/TLS Encryption @@ -338,7 +338,7 @@
    Public Key
    -
    The publicly available key in a Public Key Cryptography system, +
    The publicly available key in a Public Key Cryptography system, used to encrypt messages bound for its owner and to decrypt signatures made by its owner.
    See: SSL/TLS Encryption @@ -365,7 +365,7 @@
    Reverse Proxy
    -
    A proxy server that appears to the client +
    A proxy server that appears to the client as if it is an origin server. This is useful to hide the real origin server from the client for security reasons, or to load balance.
    @@ -418,7 +418,7 @@
    Uniform Resource Locator (URL)
    The name/address of a resource on the Internet. This is the common - informal term for what is formally called a Uniform Resource Identifier. + informal term for what is formally called a Uniform Resource Identifier. URLs are usually made up of a scheme, like http or https, a hostname, and a path. A URL for this page might be http://httpd.apache.org/docs/trunk/glossary.html. @@ -428,7 +428,7 @@ (URI)
    A compact string of characters for identifying an abstract or physical resource. It is formally defined by RFC 2396. URIs used on the - world-wide web are commonly referred to as URLs. + world-wide web are commonly referred to as URLs.
    Virtual Hosting
    @@ -446,11 +446,11 @@
    -

    Available Languages:  de  | - en  | - es  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/glossary.xml.meta b/docs/manual/glossary.xml.meta index bc5936004e..b0ea4170f5 100644 --- a/docs/manual/glossary.xml.meta +++ b/docs/manual/glossary.xml.meta @@ -2,8 +2,8 @@ glossary - /./ - .. + / + . de diff --git a/docs/manual/handler.html.en b/docs/manual/handler.html.en index a97fa2172f..7fdb0c6efe 100644 --- a/docs/manual/handler.html.en +++ b/docs/manual/handler.html.en @@ -6,35 +6,35 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Apache's Handler Use - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Apache's Handler Use

    +Apache > HTTP Server > Documentation > Version 2.3

    Apache's Handler Use

    -

    Available Languages:  en  | - es  | - ja  | - ko 

    +

    Available Languages:  en  | + es  | + ja  | + ko 

    This document describes the use of Apache's Handlers.

    -
    -
    top
    +
    top

    Examples

    @@ -119,7 +119,7 @@

    -
    top
    +
    top

    Programmer's Note

    @@ -143,11 +143,11 @@ as to not invade the media type name-space.

    -

    Available Languages:  en  | - es  | - ja  | - ko 

    +

    Available Languages:  en  | + es  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/handler.xml.meta b/docs/manual/handler.xml.meta index f202eb7b96..7aac2d6c7f 100644 --- a/docs/manual/handler.xml.meta +++ b/docs/manual/handler.xml.meta @@ -2,8 +2,8 @@ handler - /./ - .. + / + . en diff --git a/docs/manual/index.html.en b/docs/manual/index.html.en index d0366bed4d..ec7589309c 100644 --- a/docs/manual/index.html.en +++ b/docs/manual/index.html.en @@ -7,28 +7,28 @@ --> Apache HTTP Server Version 2.3 Documentation - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Apache HTTP Server Version 2.3 Documentation

    -

    Available Languages:  de  | - en  | - es  | - fr  | - ja  | - ko  | - pt-br 

    +

    Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

    Release Notes

    @@ -91,14 +91,14 @@ Documentation
    -

    Available Languages:  de  | - en  | - es  | - fr  | - ja  | - ko  | - pt-br 

    +

    Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/index.xml.meta b/docs/manual/index.xml.meta index 246456dba7..d098982bc3 100644 --- a/docs/manual/index.xml.meta +++ b/docs/manual/index.xml.meta @@ -2,8 +2,8 @@ index - /./ - .. + / + . de diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index cb71e67b6c..b2efc869a6 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -6,24 +6,24 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Compiling and Installing - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Compiling and Installing

    +Apache > HTTP Server > Documentation > Version 2.3

    Compiling and Installing

    -

    Available Languages:  de  | - en  | - es  | - fr  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko 

    @@ -40,19 +40,19 @@ example, 2.2.50 to 2.2.51), please skip down to the upgrading section.

    -
    top

    Requirements

    @@ -150,19 +150,19 @@
    Perl 5 [OPTIONAL]
    -
    For some of the support scripts like apxs or dbmmanage (which are +
    For some of the support scripts like apxs or dbmmanage (which are written in Perl) the Perl 5 interpreter is required (versions 5.003 or newer are sufficient). If you have multiple Perl interpreters (for example, a systemwide install of Perl 4, and your own install of Perl 5), you are advised to use the --with-perl option (see below) to make sure the - correct one is used by configure. + correct one is used by configure. If no Perl 5 interpreter is found by the - configure script, you will not be able to use + configure script, you will not be able to use the affected support scripts. Of course, you will still be able to build and use Apache httpd.
    -
    top
    +
    top

    Download

    @@ -182,7 +182,7 @@ page and an extended example is available describing the use of PGP.

    -
    top
    +
    top

    Extract

    @@ -198,13 +198,13 @@ $ tar xvf httpd-NN.tar containing the source code for the distribution. You should cd into that directory before proceeding with compiling the server.

    -
    top
    +
    top

    Configuring the source tree

    The next step is to configure the Apache source tree for your particular platform and personal requirements. This is done using - the script configure included in + the script configure included in the root directory of the distribution. (Developers downloading an unreleased version of the Apache source tree will need to have autoconf and libtool installed and will @@ -213,7 +213,7 @@ $ tar xvf httpd-NN.tar

    To configure the source tree using all the default options, simply type ./configure. To change the default - options, configure accepts a variety of variables + options, configure accepts a variety of variables and command line options.

    The most important option is the location --prefix @@ -233,22 +233,22 @@ $ tar xvf httpd-NN.tar --enable-module=shared. Similarly, you can disable Base modules with the --disable-module option. Be careful when - using these options, since configure cannot warn you + using these options, since configure cannot warn you if the module you specify does not exist; it will simply ignore the option.

    In addition, it is sometimes necessary to provide the - configure script with extra information about the + configure script with extra information about the location of your compiler, libraries, or header files. This is done by passing either environment variables or command line - options to configure. For more information, see the - configure manual page.

    + options to configure. For more information, see the + configure manual page.

    For a short impression of what possibilities you have, here is a typical example which compiles Apache for the installation tree /sw/pkg/apache with a particular compiler and flags - plus the two additional modules mod_rewrite and - mod_speling for + plus the two additional modules mod_rewrite and + mod_speling for later loading through the DSO mechanism:

    @@ -258,13 +258,13 @@ $ tar xvf httpd-NN.tar --enable-speling=shared

    -

    When configure is run it will take several minutes to +

    When configure is run it will take several minutes to test for the availability of features on your system and build Makefiles which will later be used to compile the server.

    -

    Details on all the different configure options are - available on the configure manual page.

    -
    top
    +

    Details on all the different configure options are + available on the configure manual page.

    +
    top

    Build

    @@ -277,7 +277,7 @@ $ tar xvf httpd-NN.tar several minutes to compile and the time will vary widely depending on your hardware and the number of modules that you have enabled.

    -
    top
    +
    top

    Install

    @@ -293,7 +293,7 @@ $ tar xvf httpd-NN.tar

    If you are upgrading, the installation will not overwrite your configuration files or documents.

    -
    top
    +
    top

    Customize

    @@ -306,7 +306,7 @@ $ tar xvf httpd-NN.tar

    Have a look at the Apache manual under PREFIX/docs/manual/ or consult http://httpd.apache.org/docs/trunk/ for the most recent version of this manual and a complete reference of available configuration directives.

    -
    top
    +
    top

    Test

    @@ -317,13 +317,13 @@ $ tar xvf httpd-NN.tar

    You should then be able to request your first document via the URL http://localhost/. The web page you see is located - under the DocumentRoot, + under the DocumentRoot, which will usually be PREFIX/htdocs/. Then stop the server again by running:

    $ PREFIX/bin/apachectl -k stop

    -
    top
    +
    top

    Upgrading

    @@ -341,9 +341,9 @@ $ tar xvf httpd-NN.tar process will not overwrite any of your existing documents, log files, or configuration files. In addition, the developers make every effort to avoid incompatible changes in the - configure options, run-time configuration, or the + configure options, run-time configuration, or the module API between minor versions. In most cases you should be able to - use an identical configure command line, an identical + use an identical configure command line, an identical configuration file, and all of your modules should continue to work.

    @@ -351,7 +351,7 @@ $ tar xvf httpd-NN.tar config.nice in the build directory of your installed server or at the root of the source tree for your old install. This will contain the exact - configure command line that you used to + configure command line that you used to configure the source tree. Then to upgrade from one version to the next, you need only copy the config.nice file to the source tree of the new version, edit it to make any desired @@ -369,11 +369,11 @@ $ tar xvf httpd-NN.tar environment before putting it into production. For example, you can install and run the new version along side the old one by using a different --prefix and a - different port (by adjusting the Listen directive) to test for any + different port (by adjusting the Listen directive) to test for any incompatibilities before doing the final upgrade.

    You can pass additional arguments to config.nice, - which will be appended to your original configure + which will be appended to your original configure options:

    @@ -381,13 +381,13 @@ $ tar xvf httpd-NN.tar

    -

    Available Languages:  de  | - en  | - es  | - fr  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/install.xml.meta b/docs/manual/install.xml.meta index d9142ee418..06f4946208 100644 --- a/docs/manual/install.xml.meta +++ b/docs/manual/install.xml.meta @@ -2,8 +2,8 @@ install - /./ - .. + / + . de diff --git a/docs/manual/invoking.html.en b/docs/manual/invoking.html.en index bf52c5cd4c..25b21b3620 100644 --- a/docs/manual/invoking.html.en +++ b/docs/manual/invoking.html.en @@ -6,23 +6,23 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Starting Apache - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Starting Apache

    -

    Available Languages:  de  | - en  | - es  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ja  | + ko 

    On Windows, Apache is normally run as a service on Windows @@ -31,21 +31,21 @@ and Running Apache as a Console Application.

    -

    On Unix, the httpd program +

    On Unix, the httpd program is run as a daemon that executes continuously in the background to handle requests. This document describes how - to invoke httpd.

    + to invoke httpd.

    - -
    top
    + +
    top

    How Apache Starts

    -

    If the Listen +

    If the Listen specified in the configuration file is default of 80 (or any other port below 1024), then it is necessary to have root privileges in order to start apache, so that it can bind to this privileged @@ -57,20 +57,20 @@ run as a less privileged user. This is controlled by the selected Multi-Processing Module.

    -

    The recommended method of invoking the httpd - executable is to use the apachectl control script. This +

    The recommended method of invoking the httpd + executable is to use the apachectl control script. This script sets certain environment variables that are necessary for - httpd to function correctly under some operating - systems, and then invokes the httpd binary. - apachectl will pass through any command line - arguments, so any httpd options may also be used with - apachectl. You may also directly edit the - apachectl script by changing the HTTPD + httpd to function correctly under some operating + systems, and then invokes the httpd binary. + apachectl will pass through any command line + arguments, so any httpd options may also be used with + apachectl. You may also directly edit the + apachectl script by changing the HTTPD variable near the top to specify the correct location of the - httpd binary and any command-line arguments that you + httpd binary and any command-line arguments that you wish to be always present.

    -

    The first thing that httpd does when it is +

    The first thing that httpd does when it is invoked is to locate and read the configuration file httpd.conf. The location of this file is set at compile-time, but it is possible to specify its location at run @@ -83,16 +83,16 @@ the terminal and the command prompt will return almost immediately. This indicates that the server is up and running. You can then use your browser to connect to the server and view - the test page in the DocumentRoot directory + the test page in the DocumentRoot directory and the local copy of the documentation linked from that page.

    -
    top
    +
    top

    Errors During Start-up

    If Apache suffers a fatal problem during startup, it will write a message describing the problem either to the console or - to the ErrorLog before + to the ErrorLog before exiting. One of the most common error messages is "Unable to bind to Port ...". This message is usually caused by either:

    @@ -108,29 +108,29 @@

    For further trouble-shooting instructions, consult the Apache FAQ.

    -
    top
    +
    top

    Starting at Boot-Time

    If you want your server to continue running after a system - reboot, you should add a call to apachectl to your + reboot, you should add a call to apachectl to your system startup files (typically rc.local or a file in an rc.N directory). This will start Apache as root. Before doing this ensure that your server is properly configured for security and access restrictions.

    -

    The apachectl script is designed to act like a +

    The apachectl script is designed to act like a standard SysV init script; it can take the arguments start, restart, and stop and translate them into the appropriate signals to - httpd. So you can often simply link - apachectl into the appropriate init directory. But be + httpd. So you can often simply link + apachectl into the appropriate init directory. But be sure to check the exact requirements of your system.

    -
    top
    +
    top

    Additional Information

    -

    Additional information about the command-line options of httpd and apachectl as well as other support +

    Additional information about the command-line options of httpd and apachectl as well as other support programs included with the server is available on the Server and Supporting Programs page. There is also documentation on all the modules included with the Apache distribution @@ -138,12 +138,12 @@ provide.

    -

    Available Languages:  de  | - en  | - es  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/invoking.xml.meta b/docs/manual/invoking.xml.meta index c747f15131..6ce3bd1e98 100644 --- a/docs/manual/invoking.xml.meta +++ b/docs/manual/invoking.xml.meta @@ -2,8 +2,8 @@ invoking - /./ - .. + / + . de diff --git a/docs/manual/license.html.en b/docs/manual/license.html.en index 571db0adc0..5af8795654 100644 --- a/docs/manual/license.html.en +++ b/docs/manual/license.html.en @@ -6,19 +6,19 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> The Apache License, Version 2.0 - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    The Apache License, Version 2.0

    +Apache > HTTP Server > Documentation > Version 2.3

    The Apache License, Version 2.0

    -

    Available Languages:  en 

    +

    Available Languages:  en 

    Apache License
    @@ -231,8 +231,8 @@ limitations under the License.

    -

    Available Languages:  en 

    +

    Available Languages:  en 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/license.xml.meta b/docs/manual/license.xml.meta index c57aca1fca..326f784edb 100644 --- a/docs/manual/license.xml.meta +++ b/docs/manual/license.xml.meta @@ -2,8 +2,8 @@ license - /./ - .. + / + . en diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en index e8b87de7b0..1481de1d08 100644 --- a/docs/manual/logs.html.en +++ b/docs/manual/logs.html.en @@ -6,21 +6,21 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Log Files - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Log Files

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    In order to effectively manage a web server, it is necessary @@ -31,15 +31,15 @@ logging capabilities, and how to understand what the logs contain.

    -
    top

    Error Log

    -
    Related ModulesRelated Directives
    +
    Related ModulesRelated Directives

    The server error log, whose name and location is set by the - ErrorLog directive, is the + ErrorLog directive, is the most important log file. This is the place where Apache httpd will send diagnostic information and record any errors that it encounters in processing requests. It is the first place to @@ -93,7 +93,7 @@

    The first item in the log entry is the date and time of the message. The second entry lists the severity of the error being - reported. The LogLevel + reported. The LogLevel directive is used to control the types of errors that are sent to the error log by restricting the severity level. The third entry gives the IP address of the client that generated the @@ -123,17 +123,17 @@

    tail -f error_log

    -
    top
    +
    top

    Access Log

    -
    Related ModulesRelated Directives
    +
    Related ModulesRelated Directives

    The server access log records all requests processed by the server. The location and content of the access log are - controlled by the CustomLog - directive. The LogFormat + controlled by the CustomLog + directive. The LogFormat directive can be used to simplify the selection of the contents of the logs. This section describes how to configure the server to record information in the access log.

    @@ -151,14 +151,14 @@

    Various versions of Apache httpd have used other modules and directives to control access logging, including mod_log_referer, mod_log_agent, and the - TransferLog directive. The CustomLog directive now subsumes + TransferLog directive. The CustomLog directive now subsumes the functionality of all the older directives.

    The format of the access log is highly configurable. The format is specified using a format string that looks much like a C-style printf(1) format string. Some examples are presented in the next sections. For a complete list of the possible contents of the - format string, see the mod_log_config format strings.

    + format string, see the mod_log_config format strings.

    Common Log Format

    @@ -183,10 +183,10 @@ control characters "\n" for new-line and "\t" for tab.

    -

    The CustomLog +

    The CustomLog directive sets up a new log file using the defined nickname. The filename for the access log is relative to - the ServerRoot unless it + the ServerRoot unless it begins with a slash.

    The above configuration will write log entries in a format @@ -206,12 +206,12 @@

    127.0.0.1 (%h)
    This is the IP address of the client (remote host) which - made the request to the server. If HostnameLookups is + made the request to the server. If HostnameLookups is set to On, then the server will try to determine the hostname and log it in place of the IP address. However, this configuration is not recommended since it can significantly slow the server. Instead, it is best to use a - log post-processor such as logresolve to determine + log post-processor such as logresolve to determine the hostnames. The IP address reported here is not necessarily the address of the machine at which the user is sitting. If a proxy server exists between the user and the @@ -227,7 +227,7 @@ machine. This information is highly unreliable and should almost never be used except on tightly controlled internal networks. Apache httpd will not even attempt to determine - this information unless IdentityCheck is set + this information unless IdentityCheck is set to On.
    frank (%u)
    @@ -350,12 +350,12 @@

    Multiple access logs can be created simply by specifying - multiple CustomLog + multiple CustomLog directives in the configuration file. For example, the following directives will create three access logs. The first contains the basic CLF information, while the second and third contain referer and browser - information. The last two CustomLog lines show how + information. The last two CustomLog lines show how to mimic the effects of the ReferLog and AgentLog directives.

    @@ -366,8 +366,8 @@

    This example also shows that it is not necessary to define a - nickname with the LogFormat directive. Instead, - the log format can be specified directly in the CustomLog directive.

    + nickname with the LogFormat directive. Instead, + the log format can be specified directly in the CustomLog directive.

    Conditional Logs

    @@ -378,8 +378,8 @@ client request. This is easily accomplished with the help of environment variables. First, an environment variable must be set to indicate that the request meets certain conditions. This is usually accomplished with - SetEnvIf. Then the - env= clause of the CustomLog directive is used to + SetEnvIf. Then the + env= clause of the CustomLog directive is used to include or exclude requests where the environment variable is set. Some examples:

    @@ -409,7 +409,7 @@ easier to simply post-process the log files to remove requests that you do not want to consider.

    -
    top
    +
    top

    Log Rotation

    @@ -444,7 +444,7 @@

    Another way to perform log rotation is using piped logs as discussed in the next section.

    -
    top
    +
    top

    Piped Logs

    @@ -468,7 +468,7 @@

    One important use of piped logs is to allow log rotation without having to restart the server. The Apache HTTP Server - includes a simple program called rotatelogs + includes a simple program called rotatelogs for this purpose. For example, to rotate the logs every 24 hours, you can use:

    @@ -489,7 +489,7 @@

    As with conditional logging, piped logs are a very powerful tool, but they should not be used where a simpler solution like off-line post-processing is available.

    -
    top
    +
    top

    Virtual Hosts

    @@ -498,16 +498,16 @@ hosts, there are several options for dealing with log files. First, it is possible to use logs exactly as in a single-host server. Simply by placing the logging directives - outside the <VirtualHost> sections in the + outside the <VirtualHost> sections in the main server context, it is possible to log all requests in the same access log and error log. This technique does not allow for easy collection of statistics on individual virtual hosts.

    -

    If CustomLog - or ErrorLog +

    If CustomLog + or ErrorLog directives are placed inside a - <VirtualHost> + <VirtualHost> section, all requests or errors for that virtual host will be logged only to the specified file. Any virtual host which does not have logging directives will still have its requests sent @@ -533,18 +533,18 @@ host that is serving the request. Then a program like split-logfile can be used to post-process the access log in order to split it into one file per virtual host.

    -
    top
    +
    top

    Other Log Files

    -
    Related ModulesRelated Directives
    +
    Related ModulesRelated Directives

    Logging actual bytes sent and recieved

    -

    mod_logio adds in two additional - LogFormat fields +

    mod_logio adds in two additional + LogFormat fields (%I and %O) that log the actual number of bytes received and sent on the network.

    @@ -552,7 +552,7 @@

    Forensic Logging

    -

    mod_log_forensic provides for forensic logging of +

    mod_log_forensic provides for forensic logging of client requests. Logging is done before and after processing a request, so the forensic log contains two log lines for each request. The forensic logger is very strict with no customizations. @@ -564,7 +564,7 @@

    On startup, Apache httpd saves the process id of the parent httpd process to the file logs/httpd.pid. This - filename can be changed with the PidFile directive. The + filename can be changed with the PidFile directive. The process-id is for use by the administrator in restarting and terminating the daemon by sending signals to the parent process; on Windows, use the -k command line option instead. @@ -576,7 +576,7 @@

    In order to aid in debugging, the - ScriptLog directive + ScriptLog directive allows you to record the input to and output from CGI scripts. This should only be used in testing - not for live servers. More information is available in the mod_cgi documentation.

    @@ -586,17 +586,17 @@

    When using the powerful and complex features of mod_rewrite, it is almost - always necessary to use the RewriteLog to help + always necessary to use the RewriteLog to help in debugging. This log file produces a detailed analysis of how the rewriting engine transforms requests. The level of detail - is controlled by the RewriteLogLevel directive.

    + is controlled by the RewriteLogLevel directive.

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/logs.xml.meta b/docs/manual/logs.xml.meta index 1bfb870b9c..675e92b994 100644 --- a/docs/manual/logs.xml.meta +++ b/docs/manual/logs.xml.meta @@ -2,8 +2,8 @@ logs - /./ - .. + / + . en diff --git a/docs/manual/mod/mod_proxy.xml.ja b/docs/manual/mod/mod_proxy.xml.ja index 9b7a149b78..df2a6757a2 100644 --- a/docs/manual/mod/mod_proxy.xml.ja +++ b/docs/manual/mod/mod_proxy.xml.ja @@ -1,7 +1,7 @@ - + Multi-Processing Modules (MPMs) - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Multi-Processing Modules (MPMs)

    +Apache > HTTP Server > Documentation > Version 2.3

    Multi-Processing Modules (MPMs)

    -

    Available Languages:  de  | - en  | - es  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ja  | + ko 

    This document describes what a Multi-Processing Module is and how they are used by the Apache HTTP Server.

    -
    • Introduction
      • -
    • Choosing an MPM
      • -
    • MPM Defaults
      • + -
      top
      +
      top

      Introduction

      @@ -60,7 +60,7 @@ how they are used by the Apache HTTP Server.

    • Apache can more cleanly and efficiently support a wide variety of operating systems. In particular, the Windows version of Apache is now much more efficient, since - mpm_winnt can use native + mpm_winnt can use native networking features in place of the POSIX layer used in Apache 1.3. This benefit also extends to other operating systems that implement specialized MPMs.
      • @@ -68,9 +68,9 @@ how they are used by the Apache HTTP Server.

    • The server can be better customized for the needs of the particular site. For example, sites that need a great deal of scalability can choose to use a threaded MPM like - worker or event, while sites requiring + worker or event, while sites requiring stability or compatibility with older software can use a - prefork.
      • + prefork.

    At the user level, MPMs appear much like other Apache @@ -78,7 +78,7 @@ how they are used by the Apache HTTP Server.

    be loaded into the server at any time. The list of available MPMs appears on the module index page.

    -
    top
    +
    top

    Choosing an MPM

    @@ -89,14 +89,14 @@ how they are used by the Apache HTTP Server.

    To actually choose the desired MPM, use the argument --with-mpm=NAME with the - configure script. NAME is the name of the + configure script. NAME is the name of the desired MPM.

    Once the server has been compiled, it is possible to determine which MPM was chosen by using ./httpd -l. This command will list every module that is compiled into the server, including the MPM.

    -
    top
    +
    top

    MPM Defaults

    @@ -106,20 +106,20 @@ choice at compile-time.

    - - - - - + + + + +
    BeOSbeos
    Netwarempm_netware
    OS/2mpmt_os2
    Unixprefork
    Windowsmpm_winnt
    BeOSbeos
    Netwarempm_netware
    OS/2mpmt_os2
    Unixprefork
    Windowsmpm_winnt
    -

    Available Languages:  de  | - en  | - es  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/mpm.xml.meta b/docs/manual/mpm.xml.meta index 7c8975a565..03696010e1 100644 --- a/docs/manual/mpm.xml.meta +++ b/docs/manual/mpm.xml.meta @@ -2,8 +2,8 @@ mpm - /./ - .. + / + . de diff --git a/docs/manual/new_features_2_0.html.en b/docs/manual/new_features_2_0.html.en index 5e26930513..20309837a7 100644 --- a/docs/manual/new_features_2_0.html.en +++ b/docs/manual/new_features_2_0.html.en @@ -6,34 +6,34 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Overview of new features in Apache 2.0 - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Overview of new features in Apache 2.0

    +Apache > HTTP Server > Documentation > Version 2.3

    Overview of new features in Apache 2.0

    -

    Available Languages:  de  | - en  | - fr  | - ja  | - ko  | - pt-br  | - ru 

    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

    This document describes some of the major changes between the 1.3 and 2.0 versions of the Apache HTTP Server.

    -
    • Core Enhancements
      • -
    • Module Enhancements
      • + -
      top
      +
      top

      Core Enhancements

      @@ -55,7 +55,7 @@
      Multiprotocol Support
      Apache now has some of the infrastructure in place to - support serving multiple protocols. mod_echo has + support serving multiple protocols. mod_echo has been written as an example.
      Better support for non-Unix @@ -81,7 +81,7 @@
      On systems where IPv6 is supported by the underlying Apache Portable Runtime library, Apache gets IPv6 listening - sockets by default. Additionally, the Listen, NameVirtualHost, and VirtualHost directives support + sockets by default. Additionally, the Listen, NameVirtualHost, and VirtualHost directives support IPv6 numeric address strings (e.g., "Listen [2001:db8::1]:8080").
      @@ -91,8 +91,8 @@ the stream of content as it is delivered to or from the server. This allows, for example, the output of CGI scripts to be parsed for Server Side Include directives using the - INCLUDES filter in mod_include. The - module mod_ext_filter allows external programs to + INCLUDES filter in mod_include. The + module mod_ext_filter allows external programs to act as filters in much the same way that CGI programs can act as handlers. @@ -106,8 +106,8 @@
      Many confusing directives have been simplified. The often confusing Port and BindAddress directives - are gone; only the Listen - directive is used for IP address binding; the ServerName directive specifies the + are gone; only the Listen + directive is used for IP address binding; the ServerName directive specifies the server name and port number only for redirection and vhost recognition.
      @@ -129,65 +129,65 @@ syntax. -
      top
      +
    top

    Module Enhancements

    -
    mod_ssl
    +
    mod_ssl
    New module in Apache 2.0. This module is an interface to the SSL/TLS encryption protocols provided by OpenSSL.
    -
    mod_dav
    +
    mod_dav
    New module in Apache 2.0. This module implements the HTTP Distributed Authoring and Versioning (DAV) specification for posting and maintaining web content.
    -
    mod_deflate
    +
    mod_deflate
    New module in Apache 2.0. This module allows supporting browsers to request that content be compressed before delivery, saving network bandwidth.
    -
    mod_auth_ldap
    +
    mod_auth_ldap
    New module in Apache 2.0.41. This module allows an LDAP database to be used to store credentials for HTTP Basic - Authentication. A companion module, mod_ldap + Authentication. A companion module, mod_ldap provides connection pooling and results caching.
    -
    mod_auth_digest
    +
    mod_auth_digest
    Includes additional support for session caching across processes using shared memory.
    -
    mod_charset_lite
    +
    mod_charset_lite
    New module in Apache 2.0. This experimental module allows for character set translation or recoding.
    -
    mod_file_cache
    +
    mod_file_cache
    New module in Apache 2.0. This module includes the functionality of mod_mmap_static in Apache 1.3, plus adds further caching abilities.
    -
    mod_headers
    +
    mod_headers
    This module is much more flexible in Apache 2.0. It can now - modify request headers used by mod_proxy, and + modify request headers used by mod_proxy, and it can conditionally set response headers.
    -
    mod_proxy
    +
    mod_proxy
    The proxy module has been completely rewritten to take advantage of the new filter infrastructure and to implement a more reliable, HTTP/1.1 compliant proxy. In addition, new - <Proxy> + <Proxy> configuration sections provide more readable (and internally faster) control of proxied sites; overloaded <Directory "proxy:..."> configuration are not supported. The module @@ -195,49 +195,49 @@ proxy_connect, proxy_ftp and proxy_http.
    -
    mod_negotiation
    +
    mod_negotiation
    -
    A new ForceLanguagePriority directive can be used to assure that +
    A new ForceLanguagePriority directive can be used to assure that the client receives a single document in all cases, rather than NOT ACCEPTABLE or MULTIPLE CHOICES responses. In addition, the negotiation and MultiViews algorithms have been cleaned up to provide more consistent results and a new form of type map that can include document content is provided.
    -
    mod_autoindex
    +
    mod_autoindex
    Autoindex'ed directory listings can now be configured to use HTML tables for cleaner formatting, and allow finer-grained control of sorting, including version-sorting, and wildcard filtering of the directory listing.
    -
    mod_include
    +
    mod_include
    New directives allow the default start and end tags for SSI elements to be changed and allow for error and time format configuration to take place in the main configuration file rather than in the SSI document. Results from regular expression parsing and grouping (now based on Perl's regular expression syntax) can be retrieved - using mod_include's variables $0 + using mod_include's variables $0 .. $9.
    -
    mod_auth_dbm
    +
    mod_auth_dbm
    Now supports multiple types of DBM-like databases using the - AuthDBMType + AuthDBMType directive.
    -

    Available Languages:  de  | - en  | - fr  | - ja  | - ko  | - pt-br  | - ru 

    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/new_features_2_0.xml.meta b/docs/manual/new_features_2_0.xml.meta index c8dfebcbe6..430fb33b27 100644 --- a/docs/manual/new_features_2_0.xml.meta +++ b/docs/manual/new_features_2_0.xml.meta @@ -2,8 +2,8 @@ new_features_2_0 - /./ - .. + / + . de diff --git a/docs/manual/new_features_2_2.html.en b/docs/manual/new_features_2_2.html.en index 0f60ba99a1..0e65a8a972 100644 --- a/docs/manual/new_features_2_2.html.en +++ b/docs/manual/new_features_2_2.html.en @@ -6,21 +6,21 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Overview of new features in Apache 2.2 - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Overview of new features in Apache 2.2

    +Apache > HTTP Server > Documentation > Version 2.3

    Overview of new features in Apache 2.2

    -

    Available Languages:  en  | - ko  | - pt-br 

    +

    Available Languages:  en  | + ko  | + pt-br 

    This document describes some of the major changes between the @@ -28,12 +28,12 @@ version 1.3, see the 2.0 new features document.

    -
    top

    Module Enhancements

    @@ -123,60 +123,60 @@
    Authn/Authz
    Modules in the aaa directory have been renamed and offer better support for digest authentication. For example, mod_auth - is now split into mod_auth_basic and - mod_auth_file; mod_auth_dbm is now called - mod_authn_dbm; mod_access has been renamed - mod_authz_host. There is also a new - mod_authn_alias module for simplifying + is now split into mod_auth_basic and + mod_auth_file; mod_auth_dbm is now called + mod_authn_dbm; mod_access has been renamed + mod_authz_host. There is also a new + mod_authn_alias module for simplifying certain authentication configurations.
    -
    mod_authnz_ldap
    +
    mod_authnz_ldap
    This module is a port of the 2.0 mod_auth_ldap module to the 2.2 Authn/Authz framework. New features include using LDAP attribute values and complicated search filters in the - Require directive.
    + Require directive. -
    mod_info
    +
    mod_info
    Added a new ?config argument which will show the configuration directives as parsed by Apache, including their file name and line number. The module also shows the order of all request hooks and additional build information, similar to httpd -V.
    -
    mod_ssl
    +
    mod_ssl
    Added a support for RFC 2817, which allows connections to upgrade from clear text to TLS encryption.
    -
    mod_imagemap
    -
    mod_imap has been renamed to mod_imagemap to avoid +
    mod_imagemap
    +
    mod_imap has been renamed to mod_imagemap to avoid user confusion.
    -
    top
    +
    top

    Program Enhancements

    -
    httpd
    +
    httpd
    A new command line option -M has been added that lists all modules that are loaded based on the current configuration. Unlike the -l option, this list - includes DSOs loaded via mod_so.
    -
    httxt2dbm
    + includes DSOs loaded via mod_so. +
    httxt2dbm
    A new program used to generate dbm files from text input, - for use in RewriteMap + for use in RewriteMap with the dbm map type.
    -
    top
    +
    top

    Module Developer Changes

    -
    APR 1.0 API
    +
    APR 1.0 API
    Apache 2.2 uses the APR 1.0 API. All deprecated functions and symbols have been removed from APR and @@ -206,7 +206,7 @@
    A new hook, test_config has been added to aid modules that want to execute special code only when the user passes - -t to httpd.
    + -t to httpd.
    Set Threaded MPM's Stacksize
    @@ -220,7 +220,7 @@
    In the past, every filter has been responsible for ensuring that it generates the correct response headers where it affects them. Filters can now delegate common protocol management to - mod_filter, using the + mod_filter, using the ap_register_output_filter_protocol or ap_filter_protocol calls.
    @@ -255,10 +255,10 @@
    -

    Available Languages:  en  | - ko  | - pt-br 

    +

    Available Languages:  en  | + ko  | + pt-br 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/new_features_2_2.xml.meta b/docs/manual/new_features_2_2.xml.meta index 8a2ead59c7..f34a8fb56e 100644 --- a/docs/manual/new_features_2_2.xml.meta +++ b/docs/manual/new_features_2_2.xml.meta @@ -2,8 +2,8 @@ new_features_2_2 - /./ - .. + / + . en diff --git a/docs/manual/new_features_2_4.html.en b/docs/manual/new_features_2_4.html.en index ba46792aa0..20c0a53d48 100644 --- a/docs/manual/new_features_2_4.html.en +++ b/docs/manual/new_features_2_4.html.en @@ -6,19 +6,19 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Overview of new features in Apache 2.4 - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Overview of new features in Apache 2.4

    +Apache > HTTP Server > Documentation > Version 2.3

    Overview of new features in Apache 2.4

    -

    Available Languages:  en 

    +

    Available Languages:  en 

    This document describes some of the major changes between the @@ -26,36 +26,36 @@ version 2.0, see the 2.2 new features document.

    -
    top

    Module Enhancements

    -
    top
    +
    top

    Program Enhancements

    -
    top
    +
    top

    Module Developer Changes

    -

    Available Languages:  en 

    +

    Available Languages:  en 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/new_features_2_4.xml.meta b/docs/manual/new_features_2_4.xml.meta index 54a404d736..f5fa37f723 100644 --- a/docs/manual/new_features_2_4.xml.meta +++ b/docs/manual/new_features_2_4.xml.meta @@ -2,8 +2,8 @@ new_features_2_4 - /./ - .. + / + . en diff --git a/docs/manual/sections.html.en b/docs/manual/sections.html.en index d1244f8ad7..df1c88d260 100644 --- a/docs/manual/sections.html.en +++ b/docs/manual/sections.html.en @@ -6,21 +6,21 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Configuration Sections - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Configuration Sections

    +Apache > HTTP Server > Documentation > Version 2.3

    Configuration Sections

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    Directives in the configuration files may apply to the entire server, or they may be restricted to apply only to particular @@ -28,31 +28,31 @@ directories, files, hosts, or URLs. This document describes how to use configuration section containers or .htaccess files to change the scope of other configuration directives.

    -
    -

    <IfDefine>, -<IfModule>, and the -<IfVersion> +

    <IfDefine>, +<IfModule>, and the +<IfVersion> can apply negative conditions by preceding their test with "!". Also, these sections can be nested to achieve more complex restrictions.

    -
    top
    +
    top

    Filesystem and Webspace

    @@ -127,11 +127,11 @@ from databases or other locations.

    Filesystem Containers

    -

    The <Directory> -and <Files> -directives, along with their regex +

    The <Directory> +and <Files> +directives, along with their regex counterparts, apply directives to -parts of the filesystem. Directives enclosed in a <Directory> section apply to +parts of the filesystem. Directives enclosed in a <Directory> section apply to the named filesystem directory and all subdirectories of that directory. The same effect can be obtained using .htaccess files. For example, in the following configuration, directory indexes will be enabled for the @@ -143,7 +143,7 @@ Options +Indexes
    </Directory>

    -

    Directives enclosed in a <Files> section apply to any file with +

    Directives enclosed in a <Files> section apply to any file with the specified name, regardless of what directory it lies in. So for example, the following configuration directives will, when placed in the main section of the configuration file, @@ -158,8 +158,8 @@ Deny from all

    To address files found in a particular part of the filesystem, the -<Files> and -<Directory> sections +<Files> and +<Directory> sections can be combined. For example, the following configuration will deny access to /var/web/dir1/private.html, /var/web/dir1/subdir2/private.html, @@ -179,8 +179,8 @@ Deny from all

    Webspace Containers

    -

    The <Location> -directive and its regex counterpart, on +

    The <Location> +directive and its regex counterpart, on the other hand, change the configuration for content in the webspace. For example, the following configuration prevents access to any URL-path that begins in /private. @@ -197,10 +197,10 @@ Deny from all
    </Location>

    -

    The <Location> +

    The <Location> directive need not have anything to do with the filesystem. For example, the following example shows how to map a particular -URL to an internal Apache handler provided by mod_status. +URL to an internal Apache handler provided by mod_status. No file called server-status needs to exist in the filesystem.

    @@ -213,9 +213,9 @@ SetHandler server-status

    Wildcards and Regular Expressions

    -

    The <Directory>, -<Files>, and -<Location> +

    The <Directory>, +<Files>, and +<Location> directives can each use shell-style wildcard characters as in fnmatch from the C standard library. The character "*" matches any sequence of characters, "?" matches any single character, @@ -224,9 +224,9 @@ character will not be matched by any wildcard; it must be specified explicitly.

    If even more flexible matching is required, each -container has a regular expression (regex) counterpart <DirectoryMatch>, <FilesMatch>, and <LocationMatch> that allow +container has a regular expression (regex) counterpart <DirectoryMatch>, <FilesMatch>, and <LocationMatch> that allow perl-compatible -regular expressions +regular expressions to be used in choosing the matches. But see the section below on configuration merging to find out how using regex sections will change how directives are applied.

    @@ -255,11 +255,11 @@ Deny from all

    Choosing between filesystem containers and webspace containers is actually quite easy. When applying directives to objects that reside -in the filesystem always use <Directory> or <Files>. When applying directives to objects +in the filesystem always use <Directory> or <Files>. When applying directives to objects that do not reside in the filesystem (such as a webpage generated from -a database), use <Location>.

    +a database), use <Location>.

    -

    It is important to never use <Location> when trying to restrict +

    It is important to never use <Location> when trying to restrict access to objects in the filesystem. This is because many different webspace locations (URLs) could map to the same filesystem location, allowing your restrictions to be circumvented. @@ -276,14 +276,14 @@ Deny from all
    http://yoursite.example.com/dir/. But what if you are on a case-insensitive filesystem? Then your restriction could be easily circumvented by requesting -http://yoursite.example.com/DIR/. The <Directory> directive, in +http://yoursite.example.com/DIR/. The <Directory> directive, in contrast, will apply to any content served from that location, regardless of how it is called. (An exception is filesystem links. The same directory can be placed in more than one part of the -filesystem using symbolic links. The <Directory> directive will follow the symbolic +filesystem using symbolic links. The <Directory> directive will follow the symbolic link without resetting the pathname. Therefore, for the highest level of security, symbolic links should be disabled with the appropriate -Options directive.)

    +Options directive.)

    If you are, perhaps, thinking that none of this applies to you because you use a case-sensitive filesystem, remember that there are @@ -295,23 +295,23 @@ rule. Putting configuration restrictions in a <Location to all requests regardless of the specific URL.

    -
    top
    +
    top

    Virtual Hosts

    -

    The <VirtualHost> +

    The <VirtualHost> container encloses directives that apply to specific hosts. This is useful when serving multiple hosts from the same machine with a different configuration for each. For more information, see the Virtual Host Documentation.

    -
    top
    +
    top

    Proxy

    -

    The <Proxy> -and <ProxyMatch> +

    The <Proxy> +and <ProxyMatch> containers apply enclosed configuration directives only -to sites accessed through mod_proxy's proxy server +to sites accessed through mod_proxy's proxy server that match the specified URL. For example, the following configuration will prevent the proxy server from being used to access the cnn.com website.

    @@ -322,39 +322,39 @@ Order allow,deny
    Deny from all
    </Proxy>

    -
    top
    +
    top

    What Directives are Allowed?

    To find out what directives are allowed in what types of configuration sections, check the Context of the directive. Everything that is allowed in -<Directory> +<Directory> sections is also syntactically allowed in -<DirectoryMatch>, -<Files>, -<FilesMatch>, -<Location>, -<LocationMatch>, -<Proxy>, -and <ProxyMatch> +<DirectoryMatch>, +<Files>, +<FilesMatch>, +<Location>, +<LocationMatch>, +<Proxy>, +and <ProxyMatch> sections. There are some exceptions, however:

    -
    top
    +
    top

    How the sections are merged

    @@ -365,40 +365,40 @@ are interpreted, it is important to understand how this works.

    The order of merging is:

      -
    1. <Directory> (except regular expressions) +
    2. <Directory> (except regular expressions) and .htaccess done simultaneously (with .htaccess, if allowed, overriding - <Directory>)
      3. + <Directory>) -
    3. <DirectoryMatch> +
    4. <DirectoryMatch> (and <Directory ~>)
      5. -
    5. <Files> and <FilesMatch> done +
    6. <Files> and <FilesMatch> done simultaneously
      7. -
    7. <Location> - and <LocationMatch> done simultaneously
      8. +
    8. <Location> + and <LocationMatch> done simultaneously
    -

    Apart from <Directory>, each group is processed in - the order that they appear in the configuration files. <Directory> (group 1 above) +

    Apart from <Directory>, each group is processed in + the order that they appear in the configuration files. <Directory> (group 1 above) is processed in the order shortest directory component to longest. So for example, <Directory /var/web/dir> will be processed before <Directory - /var/web/dir/subdir>. If multiple <Directory> sections apply + /var/web/dir/subdir>. If multiple <Directory> sections apply to the same directory they are processed in the configuration file - order. Configurations included via the Include directive will be treated as if + order. Configurations included via the Include directive will be treated as if they were inside the including file at the location of the - Include directive.

    + Include directive.

    -

    Sections inside <VirtualHost> sections +

    Sections inside <VirtualHost> sections are applied after the corresponding sections outside the virtual host definition. This allows virtual hosts to override the main server configuration.

    -

    When the request is served by mod_proxy, the - <Proxy> - container takes the place of the <Directory> container in the processing +

    When the request is served by mod_proxy, the + <Proxy> + container takes the place of the <Directory> container in the processing order.

    Later sections override earlier ones.

    @@ -446,7 +446,7 @@ A

    For a more concrete example, consider the following. Regardless of -any access restrictions placed in <Directory> sections, the <Location> section will be +any access restrictions placed in <Directory> sections, the <Location> section will be evaluated last and will allow unrestricted access to the server. In other words, order of merging is important, so be careful!

    @@ -468,10 +468,10 @@ Deny from badguy.example.com
    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/sections.xml.meta b/docs/manual/sections.xml.meta index a4075a688c..b372be7151 100644 --- a/docs/manual/sections.xml.meta +++ b/docs/manual/sections.xml.meta @@ -2,8 +2,8 @@ sections - /./ - .. + / + . en diff --git a/docs/manual/server-wide.html.en b/docs/manual/server-wide.html.en index 87f5f6e229..e74c989792 100644 --- a/docs/manual/server-wide.html.en +++ b/docs/manual/server-wide.html.en @@ -6,74 +6,74 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Server-Wide Configuration - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Server-Wide Configuration

    +Apache > HTTP Server > Documentation > Version 2.3

    Server-Wide Configuration

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    This document explains some of the directives provided by -the core server which are used to configure +the core server which are used to configure the basic operations of the server.

    -
    top

    File Locations

    -
    Related ModulesRelated Directives
    +
    Related ModulesRelated Directives

    These directives control the locations of the various files that Apache needs for proper operation. When the pathname used does not begin with a slash (/), the files are located relative - to the ServerRoot. Be careful + to the ServerRoot. Be careful about locating files in paths which are writable by non-root users. See the security tips documentation for more details.

    -
    top
    +
    top

    Limiting Resource Usage

    -
    Related ModulesRelated Directives
    +
    Related ModulesRelated Directives

    The LimitRequest* directives are used to place limits on the amount of resources @@ -87,14 +87,14 @@ the basic operations of the server.

    this will control resources used by CGI scripts and SSI exec commands.

    -

    The ThreadStackSize +

    The ThreadStackSize directive is used with some platforms to control the stack size.

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/server-wide.xml.meta b/docs/manual/server-wide.xml.meta index b3fa2d900b..b7f3c1db76 100644 --- a/docs/manual/server-wide.xml.meta +++ b/docs/manual/server-wide.xml.meta @@ -2,8 +2,8 @@ server-wide - /./ - .. + / + . en diff --git a/docs/manual/sitemap.html.en b/docs/manual/sitemap.html.en index 1ff40e5166..e4c5fcae53 100644 --- a/docs/manual/sitemap.html.en +++ b/docs/manual/sitemap.html.en @@ -6,25 +6,25 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Sitemap - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-
    +Apache > HTTP Server > Documentation > Version 2.3

    Sitemap

    -

    Available Languages:  de  | - en  | - es  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ja  | + ko 

    This page lists the currently available documents of the @@ -32,21 +32,21 @@ Documentation.

    -
    top
    +
    top

    Release Notes

    -
    top
    +
    top

    Using the Apache HTTP Server

    -
    top
    +
    top

    Apache Virtual Host documentation

    -
    top
    +
    top

    Apache Server Frequently Asked Questions

    -
    top
    +
    top

    Apache SSL/TLS Encryption

    -
    top
    +
    top

    Guides, Tutorials, and HowTos

    -
    top
    +
    top

    Platform-specific Notes

    -
    top
    +
    top

    Apache HTTP Server and Supporting Programs

    -
    top
    +
    top

    Apache Miscellaneous Documentation

    -
    top
    +
    top

    Apache modules

    -
    top
    +
    top

    Developer Documentation

    -
    top
    +
    top

    Glossary and Index

    -

    Available Languages:  de  | - en  | - es  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/sitemap.xml.meta b/docs/manual/sitemap.xml.meta index a69732a951..4e2470686c 100644 --- a/docs/manual/sitemap.xml.meta +++ b/docs/manual/sitemap.xml.meta @@ -2,8 +2,8 @@ sitemap - /./ - .. + / + . de diff --git a/docs/manual/stopping.html.en b/docs/manual/stopping.html.en index d0ccf3c453..3e017cc1e6 100644 --- a/docs/manual/stopping.html.en +++ b/docs/manual/stopping.html.en @@ -6,23 +6,23 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Stopping and Restarting - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Stopping and Restarting

    +Apache > HTTP Server > Documentation > Version 2.3

    Stopping and Restarting

    -

    Available Languages:  de  | - en  | - es  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ja  | + ko 

    This document covers stopping and restarting Apache on @@ -32,23 +32,23 @@ Console Application for information on how to control Apache on those platforms.

    - -
    top
    + +
    top

    Introduction

    In order to stop or restart Apache, you must send a signal to - the running httpd processes. There are two ways to + the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will - notice many httpd executables running on your system, + notice many httpd executables running on your system, but you should not send signals to any of them except the parent, - whose pid is in the PidFile. That is to say you + whose pid is in the PidFile. That is to say you shouldn't ever need to send signals to any process except the parent. There are four signals that you can send the parent: TERM, @@ -62,20 +62,20 @@

    kill -TERM `cat /usr/local/apache2/logs/httpd.pid`

    -

    The second method of signaling the httpd processes +

    The second method of signaling the httpd processes is to use the -k command line options: stop, restart, graceful and graceful-stop, - as described below. These are arguments to the httpd binary, but we recommend that - you send them using the apachectl control script, which - will pass them through to httpd.

    + as described below. These are arguments to the httpd binary, but we recommend that + you send them using the apachectl control script, which + will pass them through to httpd.

    -

    After you have signaled httpd, you can read about +

    After you have signaled httpd, you can read about its progress by issuing:

    tail -f /usr/local/apache2/logs/error_log

    -

    Modify those examples to match your ServerRoot and PidFile settings.

    -
    top
    +

    Modify those examples to match your ServerRoot and PidFile settings.

    +
    top

    Stop Now

    @@ -88,7 +88,7 @@ children. It may take it several seconds to complete killing off its children. Then the parent itself exits. Any requests in progress are terminated, and no further requests are served.

    -
    top
    +
    top

    Graceful Restart

    @@ -108,15 +108,15 @@ directive of the MPMs, so the number of processes and threads available to serve clients will be maintained at the appropriate values throughout the restart process. Furthermore, it respects - StartServers in the - following manner: if after one second at least StartServers new children have not + StartServers in the + following manner: if after one second at least StartServers new children have not been created, then create enough to pick up the slack. Hence the code tries to maintain both the number of children appropriate for the current load on the server, and respect your wishes with the - StartServers + StartServers parameter.

    -

    Users of mod_status +

    Users of mod_status will notice that the server statistics are not set to zero when a USR1 is sent. The code was written to both minimize the time in which the server is unable @@ -150,13 +150,13 @@

    This still will not guarantee that the server will restart correctly. To check the semantics of the configuration files as well as the syntax, you - can try starting httpd as a non-root user. If there + can try starting httpd as a non-root user. If there are no errors it will attempt to open its sockets and logs and fail because it's not root (or because the currently running - httpd already has those ports bound). If it fails + httpd already has those ports bound). If it fails for any other reason then it's probably a config file error and the error should be fixed before issuing the graceful restart.

    -
    top
    +
    top

    Restart Now

    @@ -170,7 +170,7 @@ configuration files, and re-opens any log files. Then it spawns a new set of children and continues serving hits.

    -

    Users of mod_status +

    Users of mod_status will notice that the server statistics are set to zero when a HUP is sent.

    @@ -178,7 +178,7 @@ restart is attempted. If your configuration file has errors in it, the restart will not be attempted, and you will receive notification of the syntax error(s).
    -
    top
    +
    top

    Graceful Stop

    @@ -189,45 +189,45 @@ syntax error(s).

    The WINCH or graceful-stop signal causes the parent process to advise the children to exit after their current request (or to exit immediately if they're not - serving anything). The parent will then remove its PidFile and cease listening on + serving anything). The parent will then remove its PidFile and cease listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised - and exited or the timeout specified by the GracefulShutdownTimeout has been + and exited or the timeout specified by the GracefulShutdownTimeout has been reached, the parent will also exit. If the timeout is reached, any remaining children will be sent the TERM signal to force them to exit.

    A TERM signal will immediately terminate the parent process and all children when in the "graceful" state. However - as the PidFile will + as the PidFile will have been removed, you will not be able to use apachectl or httpd to send this signal,

    The graceful-stop signal allows you to run multiple - identically configured instances of httpd at the + identically configured instances of httpd at the same time. This is a powerful feature when performing graceful upgrades of Apache, however it can also cause deadlocks and race conditions with some configurations.

    Care has been taken to ensure that on-disk files - such as the Lockfile and ScriptSock files contain the server + such as the Lockfile and ScriptSock files contain the server PID, and should co-exist without problem. However, if a configuration directive, third-party module or persistent CGI utilises any other on-disk lock or state files; care should be taken to ensure that multiple running - instances of httpd do not clobber each others files.

    + instances of httpd do not clobber each others files.

    You should also be wary of other potential race conditions, such as - using rotatelogs style piped logging. Multiple running - instances of rotatelogs attempting to rotate the same + using rotatelogs style piped logging. Multiple running + instances of rotatelogs attempting to rotate the same logfiles at the same time may destroy each other's logfiles.

    -

    Available Languages:  de  | - en  | - es  | - ja  | - ko 

    +

    Available Languages:  de  | + en  | + es  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/stopping.xml.meta b/docs/manual/stopping.xml.meta index 2735fe1739..df2dbd4991 100644 --- a/docs/manual/stopping.xml.meta +++ b/docs/manual/stopping.xml.meta @@ -2,8 +2,8 @@ stopping - /./ - .. + / + . de diff --git a/docs/manual/suexec.html.en b/docs/manual/suexec.html.en index 881ff9d494..3f22a6ce8e 100644 --- a/docs/manual/suexec.html.en +++ b/docs/manual/suexec.html.en @@ -6,21 +6,21 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> suEXEC Support - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    suEXEC Support

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    The suEXEC feature provides @@ -39,18 +39,18 @@ and the security issues they present, we highly recommend that you not consider using suEXEC.

    -
    top

    suEXEC Security Model

    @@ -348,7 +348,7 @@ configuration, as well as what security risks can be avoided with a proper suEXEC setup, see the "Beware the Jabberwock" section of this document.

    -
    top
    +
    top

    Configuring & Installing suEXEC

    @@ -456,7 +456,7 @@

    Setting paranoid permissions
    Although the suEXEC wrapper will check to ensure that its caller is the correct user as specified with the - --with-suexec-caller configure + --with-suexec-caller configure option, there is always the possibility that a system or library call suEXEC uses before this check may be exploitable on your system. To counter @@ -471,7 +471,7 @@ Group webgroup

    -

    and suexec is installed at +

    and suexec is installed at "/usr/local/apache2/sbin/suexec", you should run:

    @@ -481,13 +481,13 @@

    This will ensure that only the group Apache runs as can even execute the suEXEC wrapper.

    -
    top
    +
    top

    Enabling & Disabling suEXEC

    Upon startup of Apache, it looks for the file - suexec in the directory defined by the + suexec in the directory defined by the --sbindir option (default is "/usr/local/apache/sbin/suexec"). If Apache finds a properly configured suEXEC wrapper, it will print the following message @@ -506,33 +506,33 @@ restart Apache. Restarting it with a simple HUP or USR1 signal will not be enough.

    If you want to disable suEXEC you should kill and restart - Apache after you have removed the suexec file.

    -
    top
    + Apache after you have removed the suexec file.

    +
    top

    Using suEXEC

    Requests for CGI programs will call the suEXEC wrapper only if - they are for a virtual host containing a SuexecUserGroup directive or if - they are processed by mod_userdir.

    + they are for a virtual host containing a SuexecUserGroup directive or if + they are processed by mod_userdir.

    Virtual Hosts:
    One way to use the suEXEC - wrapper is through the SuexecUserGroup directive in - VirtualHost definitions. By + wrapper is through the SuexecUserGroup directive in + VirtualHost definitions. By setting this directive to values different from the main server user ID, all requests for CGI resources will be executed as the - User and Group defined for that <VirtualHost>. If this - directive is not specified for a <VirtualHost> then the main server userid + User and Group defined for that <VirtualHost>. If this + directive is not specified for a <VirtualHost> then the main server userid is assumed.

    User directories:
    Requests that are - processed by mod_userdir will call the suEXEC + processed by mod_userdir will call the suEXEC wrapper to execute CGI programs under the userid of the requested user directory. The only requirement needed for this feature to work is for CGI execution to be enabled for the user and that the script must meet the scrutiny of the security checks above. See also the --with-suexec-userdir compile - time option.

    top
    + time option.

    top

    Debugging suEXEC

    @@ -542,7 +542,7 @@ installed the wrapper properly, have a look at this log and the error_log for the server to see where you may have gone astray.

    -
    top
    +
    top

    Beware the Jabberwock: Warnings & Examples

    @@ -599,10 +599,10 @@
    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/suexec.xml.meta b/docs/manual/suexec.xml.meta index 54e90e163d..e0cc057f5b 100644 --- a/docs/manual/suexec.xml.meta +++ b/docs/manual/suexec.xml.meta @@ -2,8 +2,8 @@ suexec - /./ - .. + / + . en diff --git a/docs/manual/upgrading.html.en b/docs/manual/upgrading.html.en index a18541b5ed..017bf174e9 100644 --- a/docs/manual/upgrading.html.en +++ b/docs/manual/upgrading.html.en @@ -6,24 +6,24 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Upgrading to 2.4 from 2.2 - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Upgrading to 2.4 from 2.2

    +Apache > HTTP Server > Documentation > Version 2.3

    Upgrading to 2.4 from 2.2

    -

    Available Languages:  de  | - en  | - ja  | - ko  | - pt-br  | - ru 

    +

    Available Languages:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    In order to assist folks upgrading, we maintain a document @@ -37,43 +37,43 @@ upgrading document.

    -
    top

    Run-Time Configuration Changes

    -
    top
    +
    top

    Misc Changes

    -
    top
    +
    top

    Third Party Modules

    -

    Available Languages:  de  | - en  | - ja  | - ko  | - pt-br  | - ru 

    +

    Available Languages:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/upgrading.xml.meta b/docs/manual/upgrading.xml.meta index 5791bc3eff..636b2b1051 100644 --- a/docs/manual/upgrading.xml.meta +++ b/docs/manual/upgrading.xml.meta @@ -2,8 +2,8 @@ upgrading - /./ - .. + / + . de diff --git a/docs/manual/urlmapping.html.en b/docs/manual/urlmapping.html.en index b45e6438f4..33ea3070f1 100644 --- a/docs/manual/urlmapping.html.en +++ b/docs/manual/urlmapping.html.en @@ -6,55 +6,55 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> Mapping URLs to Filesystem Locations - Apache HTTP Server - - - - + + + +
    -

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.3

    -
    -
    <-
    + +
    <-

    Mapping URLs to Filesystem Locations

    +Apache > HTTP Server > Documentation > Version 2.3

    Mapping URLs to Filesystem Locations

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    This document explains how Apache uses the URL of a request to determine the filesystem location from which to serve a file.

    -
    top

    DocumentRoot

    In deciding what file to serve for a given request, Apache's default behavior is to take the URL-Path for the request (the part of the URL following the hostname and port) and add it to the end - of the DocumentRoot specified + of the DocumentRoot specified in your configuration files. Therefore, the files and directories - underneath the DocumentRoot + underneath the DocumentRoot make up the basic document tree which will be visible from the web.

    -

    For example, if DocumentRoot +

    For example, if DocumentRoot were set to /var/www/html then a request for http://www.example.com/fish/guppies.html would result in the file /var/www/html/fish/guppies.html being @@ -62,44 +62,44 @@

    Apache is also capable of Virtual Hosting, where the server receives requests for more than one - host. In this case, a different DocumentRoot can be specified for each + host. In this case, a different DocumentRoot can be specified for each virtual host, or alternatively, the directives provided by the - module mod_vhost_alias can + module mod_vhost_alias can be used to dynamically determine the appropriate place from which to serve content based on the requested IP address or hostname.

    -

    The DocumentRoot directive +

    The DocumentRoot directive is set in your main server configuration file (httpd.conf) and, possibly, once per additional Virtual Host you create.

    -
    top
    +
    top

    Files Outside the DocumentRoot

    There are frequently circumstances where it is necessary to allow web access to parts of the filesystem that are not strictly - underneath the DocumentRoot. Apache offers several + underneath the DocumentRoot. Apache offers several different ways to accomplish this. On Unix systems, symbolic links - can bring other parts of the filesystem under the DocumentRoot. For security reasons, - Apache will follow symbolic links only if the Options setting for the relevant + can bring other parts of the filesystem under the DocumentRoot. For security reasons, + Apache will follow symbolic links only if the Options setting for the relevant directory includes FollowSymLinks or SymLinksIfOwnerMatch.

    -

    Alternatively, the Alias directive will map any part +

    Alternatively, the Alias directive will map any part of the filesystem into the web space. For example, with

    Alias /docs /var/web

    the URL http://www.example.com/docs/dir/file.html will be served from /var/web/dir/file.html. The - ScriptAlias directive + ScriptAlias directive works the same way, with the additional effect that all content - located at the target path is treated as CGI scripts.

    + located at the target path is treated as CGI scripts.

    For situations where you require additional flexibility, you - can use the AliasMatch - and ScriptAliasMatch - directives to do powerful regular + can use the AliasMatch + and ScriptAliasMatch + directives to do powerful regular expression based matching and substitution. For example,

    @@ -110,13 +110,13 @@ http://example.com/~user/cgi-bin/script.cgi to the path /home/user/cgi-bin/script.cgi and will treat the resulting file as a CGI script.

    -
    top
    +
    top

    User Directories

    Traditionally on Unix systems, the home directory of a particular user can be referred to as - ~user/. The module mod_userdir + ~user/. The module mod_userdir extends this idea to the web by allowing files under each user's home directory to be accessed using URLs such as the following.

    @@ -125,7 +125,7 @@

    For security reasons, it is inappropriate to give direct access to a user's home directory from the web. Therefore, the - UserDir directive + UserDir directive specifies a directory underneath the user's home directory where web files are located. Using the default setting of Userdir public_html, the above URL maps to a file @@ -144,7 +144,7 @@ alternate string to represent user directories. This functionality is not supported by mod_userdir. However, if users' home directories are structured in a regular way, then it is possible - to use the AliasMatch + to use the AliasMatch directive to achieve the desired effect. For example, to make http://www.example.com/upages/user/file.html map to /home/user/public_html/file.html, use the following @@ -152,7 +152,7 @@

    AliasMatch ^/upages/([a-zA-Z0-9]+)/?(.*) /home/$1/public_html/$2

    -
    top
    +
    top

    URL Redirection

    @@ -162,9 +162,9 @@ inform the client that the requested content is located at a different URL, and instruct the client to make a new request with the new URL. This is called redirection and is - implemented by the Redirect directive. For example, if + implemented by the Redirect directive. For example, if the contents of the directory /foo/ under the - DocumentRoot are moved + DocumentRoot are moved to the new directory /bar/, you can instruct clients to request the content at the new location as follows:

    @@ -177,7 +177,7 @@ substituted for /foo/. You can redirect clients to any server, not only the origin server.

    -

    Apache also provides a RedirectMatch directive for more +

    Apache also provides a RedirectMatch directive for more complicated rewriting problems. For example, to redirect requests for the site home page to a different site, but leave all other requests alone, use the following configuration:

    @@ -190,7 +190,7 @@

    RedirectMatch temp .* http://othersite.example.com/startpage.html

    -
    top
    +
    top

    Reverse Proxy

    @@ -214,14 +214,14 @@ ProxyPassReverseCookieDomain internal.example.com public.example.com ProxyPassReverseCookiePath /foo/ /bar/

    -

    The ProxyPass configures +

    The ProxyPass configures the server to fetch the appropriate documents, while the -ProxyPassReverse +ProxyPassReverse directive rewrites redirects originating at internal.example.com so that they target the appropriate directory on the local server. Similarly, the -ProxyPassReverseCookieDomain -and ProxyPassReverseCookieDomain +ProxyPassReverseCookieDomain +and ProxyPassReverseCookieDomain rewrite cookies set by the backend server.

    It is important to note, however, that links inside the documents will not be rewritten. So any absolute @@ -230,12 +230,12 @@ breaking out of the proxy server and requesting directly from internal.example.com. A third-party module mod_proxy_html is available to rewrite links in HTML and XHTML.

    -
    top
    +
    top

    Rewriting Engine

    When even more powerful substitution is required, the rewriting - engine provided by mod_rewrite + engine provided by mod_rewrite can be useful. The directives provided by this module use characteristics of the request such as browser type or source IP address in deciding from where to serve content. In addition, @@ -245,7 +245,7 @@ is available to rewrite links in HTML and XHTML.

    internal redirects (aliases), external redirects, and proxying. Many practical examples employing mod_rewrite are discussed in the URL Rewriting Guide.

    -
    top
    +
    top

    File Not Found

    @@ -261,7 +261,7 @@ is available to rewrite links in HTML and XHTML.

    Another common cause of "File Not Found" errors is accidental mistyping of URLs, either directly in the browser, or in HTML links. Apache provides the module - mod_speling (sic) to help with + mod_speling (sic) to help with this problem. When this module is activated, it will intercept "File Not Found" errors and look for a resource with a similar filename. If one such file is found, mod_speling will send an @@ -281,16 +281,16 @@ is available to rewrite links in HTML and XHTML.

    If all attempts to locate the content fail, Apache returns an error page with HTTP status code 404 (file not found). The appearance of this page is controlled with the - ErrorDocument directive + ErrorDocument directive and can be customized in a flexible manner as discussed in the Custom error responses document.

    -

    Available Languages:  en  | - ja  | - ko 

    +

    Available Languages:  en  | + ja  | + ko 

    +

    Modules | Directives | FAQ | Glossary | Sitemap

    \ No newline at end of file diff --git a/docs/manual/urlmapping.xml.meta b/docs/manual/urlmapping.xml.meta index 4f3697fe41..f31114d930 100644 --- a/docs/manual/urlmapping.xml.meta +++ b/docs/manual/urlmapping.xml.meta @@ -2,8 +2,8 @@ urlmapping - /./ - .. + / + . en