From: Rich Bowen Date: Tue, 23 Mar 2010 02:19:20 +0000 (+0000) Subject: 'Apache' => 'Apache HTTP Server' X-Git-Tag: 2.3.6~306 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6588ab5a5b3001c3102c1ec52da9c79789a267aa;p=thirdparty%2Fapache%2Fhttpd.git 'Apache' => 'Apache HTTP Server' git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@926430 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index be00cfe436a..ceaf8c5a67b 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -36,14 +36,14 @@ network and to the Internet at large.

-

This module implements a proxy/gateway for Apache. It implements +

This module implements a proxy/gateway for Apache HTTP Server. It implements proxying capability for AJP13 (Apache JServe Protocol version 1.3), FTP, CONNECT (for SSL), HTTP/0.9, HTTP/1.0, and HTTP/1.1. The module can be configured to connect to other proxy modules for these and other protocols.

-

Apache's proxy features are divided into several modules in +

Apache httpd's proxy features are divided into several modules in addition to mod_proxy: mod_proxy_http, mod_proxy_ftp, mod_proxy_ajp, mod_proxy_balancer, @@ -113,7 +113,7 @@

Forward Proxies and Reverse Proxies/Gateways

-

Apache can be configured in both a forward and +

Apache HTTP Server can be configured in both a forward and reverse proxy (also known as gateway) mode.

An ordinary forward proxy is an intermediate @@ -234,7 +234,7 @@

top

Intranet Proxy

-

An Apache proxy server situated in an intranet needs to forward +

An Apache httpd proxy server situated in an intranet needs to forward external requests through the company's firewall (for this, configure the ProxyRemote directive to forward the respective scheme to the firewall proxy). @@ -248,7 +248,7 @@ WWW requests, thus requesting "http://somehost/" instead of http://somehost.example.com/. Some commercial proxy servers let them get away with this and simply serve the request, implying a - configured local domain. When the ProxyDomain directive is used and the server is configured for proxy service, Apache can return + configured local domain. When the ProxyDomain directive is used and the server is configured for proxy service, Apache httpd can return a redirect response and send the client to the correct, fully qualified, server address. This is the preferred method since the user's bookmark files will then contain fully qualified hosts.

@@ -332,7 +332,7 @@ Context:directory Status:Extension Module:mod_proxy -Compatibility:BalancerMember is only available in Apache 2.2 +Compatibility:BalancerMember is only available in Apache HTTP Server 2.2 and later.

This directive adds a member to a load balancing group. It could be used @@ -358,7 +358,7 @@ directly Status:Extension Module:mod_proxy -

This directive is only useful for Apache proxy servers within +

This directive is only useful for Apache httpd proxy servers within intranets. The NoProxy directive specifies a list of subnets, IP addresses, hosts and/or domains, separated by spaces. A request to a host which matches one or more of these is @@ -457,7 +457,7 @@ directly

Note

In many situations, it is more effective to specify an IPAddr in place of a Hostname since a - DNS lookup can be avoided. Name resolution in Apache can take a remarkable + DNS lookup can be avoided. Name resolution in Apache httpd can take a remarkable deal of time when the connection to the name server uses a slow PPP link.

Hostname comparisons are done without regard to the case, @@ -528,7 +528,7 @@ response Context:server config, virtual host Status:Extension Module:mod_proxy -Compatibility:Available in Apache 2.0.44 and later +Compatibility:Available in Apache HTTP Server 2.0.44 and later

The ProxyBadHeader directive determines the behaviour of mod_proxy if it receives syntactically invalid @@ -597,7 +597,7 @@ proxied Status:Extension Module:mod_proxy -

This directive is only useful for Apache proxy servers within +

This directive is only useful for Apache httpd proxy servers within intranets. The ProxyDomain directive specifies the default domain which the apache proxy server will belong to. If a request to a host without a domain name is encountered, a redirection @@ -689,7 +689,7 @@ through Context:server config, virtual host Status:Extension Module:mod_proxy -Compatibility:Available in Apache 2.0 and later; +Compatibility:Available in Apache HTTP Server 2.0 and later; default behaviour changed in 2.2.7/2.3

The ProxyMaxForwards directive specifies the @@ -704,7 +704,7 @@ through

Note that setting ProxyMaxForwards is a violation of the HTTP/1.1 protocol (RFC2616), which forbids a Proxy setting Max-Forwards if the Client didn't set it. - Earlier Apache versions would always set it. A negative + Earlier Apache httpd versions would always set it. A negative ProxyMaxForwards value, including the default -1, gives you protocol-compliant behaviour, but may leave you open to loops.

@@ -768,7 +768,7 @@ through general ProxyPass directive.

-

As of Apache 2.1, the ability to use pooled connections to a backend +

As of Apache HTTP Server 2.1, the ability to use pooled connections to a backend server is available. Using the key=value parameters it is possible to tune this connection pooling. The default for a Hard Maximum for the number of connections is the number of threads per @@ -779,7 +779,7 @@ through

Setting min will determine how many connections will always be open to the backend server. Upto the Soft Maximum or smax number of connections will be created on demand. Any connections above - smax are subject to a time to live or ttl. Apache + smax are subject to a time to live or ttl. Apache httpd will never create more than the Hard Maximum or max connections to the backend server.

@@ -802,7 +802,7 @@ through for the number of connections is the number of threads per process in the active MPM. In the Prefork MPM, this is always 1, while with the Worker MPM it is controlled by the ThreadsPerChild. - Apache will never create more than the Hard Maximum connections + Apache httpd will never create more than the Hard Maximum connections to the backend server. smax max @@ -814,13 +814,13 @@ through - If set this will be the maximum time to wait for a free connection in the connection pool, in milliseconds. If there are no free - connections in the pool the Apache will return SERVER_BUSY + connections in the pool the Apache httpd will return SERVER_BUSY status to the client. connectiontimeout timeout Connect timeout in seconds. - The number of seconds Apache waits for the creation of a connection to + The number of seconds Apache httpd waits for the creation of a connection to the backend to complete. By adding a postfix of ms the timeout can be also set in milliseconds. @@ -829,7 +829,8 @@ through This parameter should be used when you want to force mod_proxy to immediately close a connection to the backend after being used, and thus, disable its persistent connection and pool for that backend. - This helps in various situations where a firewall between Apache and + This helps in various situations where a firewall between Apache + httpd and the backend server (regardless of protocol) tends to silently drop connections or when backends themselves may be under round- robin DNS. To disable connection pooling reuse, @@ -858,7 +859,7 @@ through keepalive Off This parameter should be used when you have a firewall between your - Apache and the backend server, who tend to drop inactive connections. + Apache httpd and the backend server, who tend to drop inactive connections. This flag will tell the Operating System to send KEEP_ALIVE messages on inactive connections (interval depends on global OS settings, generally 120ms), and thus prevent the firewall to drop the connection. @@ -905,7 +906,7 @@ through 60 Connection pool worker retry timeout in seconds. If the connection pool worker to the backend server is in the error state, - Apache will not forward any requests to that server until the timeout + Apache httpd will not forward any requests to that server until the timeout expires. This enables to shut down the backend server for maintenance, and bring it back online later. A value of 0 means always retry workers in an error state with no timeout. @@ -928,12 +929,12 @@ through timeout ProxyTimeout Connection timeout in seconds. - The number of seconds Apache waits for data sent by / to the backend. + The number of seconds Apache httpd waits for data sent by / to the backend. ttl - Time To Live for the inactive connections above the - smax connections in seconds. Apache will close all + smax connections in seconds. Apache httpd will close all connections that has not been used inside that time period. @@ -1129,15 +1130,15 @@ proxied server Status:Extension Module:mod_proxy -

This directive lets Apache adjust the URL in the Location, +

This directive lets Apache httpd adjust the URL in the Location, Content-Location and URI headers on HTTP - redirect responses. This is essential when Apache is used as a + redirect responses. This is essential when Apache httpd is used as a reverse proxy (or gateway) to avoid by-passing the reverse proxy because of HTTP redirects on the backend servers which stay behind the reverse proxy.

Only the HTTP response headers specifically mentioned above - will be rewritten. Apache will not rewrite other response + will be rewritten. Apache httpd will not rewrite other response headers, nor will it rewrite URL references inside HTML pages. This means that if the proxied content contains absolute URL references, they will by-pass the proxy. A third-party module @@ -1164,7 +1165,7 @@ proxied server (the functionality ProxyPass provides here). It also takes care of redirects the server backend.example.com sends: when http://backend.example.com/bar is redirected by him to - http://backend.example.com/quux Apache adjusts this to + http://backend.example.com/quux Apache httpd adjusts this to http://example.com/mirror/foo/quux before forwarding the HTTP redirect response to the client. Note that the hostname used for constructing the URL is chosen in respect to the setting of the UseCanonicalName directive.

@@ -1228,7 +1229,7 @@ request Context:server config, virtual host, directory Status:Extension Module:mod_proxy -Compatibility:Available in Apache 2.0.31 and later. Usable in directory +Compatibility:Available in Apache HTTP Server 2.0.31 and later. Usable in directory context in 2.3.3 and later.

When enabled, this option will pass the Host: line from the incoming @@ -1329,7 +1330,7 @@ expressions Status:Extension Module:mod_proxy -

This allows or prevents Apache from functioning as a forward proxy +

This allows or prevents Apache httpd from functioning as a forward proxy server. (Setting ProxyRequests to Off does not disable use of the ProxyPass directive.)

@@ -1359,7 +1360,7 @@ expressions Context:directory Status:Extension Module:mod_proxy -Compatibility:ProxySet is only available in Apache 2.2 +Compatibility:ProxySet is only available in Apache HTTP Server 2.2 and later.

This directive is used as an alternate method of setting any of the @@ -1435,7 +1436,7 @@ expressions Context:server config, virtual host Status:Extension Module:mod_proxy -Compatibility:Available in Apache 2.0.31 and later +Compatibility:Available in Apache HTTP Server 2.0.31 and later

This directive allows a user to specifiy a timeout on proxy requests. This is useful when you have a slow/buggy appserver which hangs, and you @@ -1468,7 +1469,7 @@ header for proxied requests Via: header line added for the current host.

  • If set to Full, each generated Via: header - line will additionally have the Apache server version shown as a + line will additionally have the Apache httpd server version shown as a Via: comment field.
  • If set to Block, every proxy request will have all its diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml index 738c6d55ec2..a4218f4126b 100644 --- a/docs/manual/mod/mod_proxy.xml +++ b/docs/manual/mod/mod_proxy.xml @@ -36,14 +36,14 @@ network and to the Internet at large.

    -

    This module implements a proxy/gateway for Apache. It implements +

    This module implements a proxy/gateway for Apache HTTP Server. It implements proxying capability for AJP13 (Apache JServe Protocol version 1.3), FTP, CONNECT (for SSL), HTTP/0.9, HTTP/1.0, and HTTP/1.1. The module can be configured to connect to other proxy modules for these and other protocols.

    -

    Apache's proxy features are divided into several modules in +

    Apache httpd's proxy features are divided into several modules in addition to mod_proxy: mod_proxy_http, mod_proxy_ftp, mod_proxy_ajp, mod_proxy_balancer, @@ -70,7 +70,7 @@

    Forward Proxies and Reverse Proxies/Gateways -

    Apache can be configured in both a forward and +

    Apache HTTP Server can be configured in both a forward and reverse proxy (also known as gateway) mode.

    An ordinary forward proxy is an intermediate @@ -201,7 +201,7 @@

    Intranet Proxy -

    An Apache proxy server situated in an intranet needs to forward +

    An Apache httpd proxy server situated in an intranet needs to forward external requests through the company's firewall (for this, configure the ProxyRemote directive to forward the respective scheme to the firewall proxy). @@ -217,7 +217,7 @@ let them get away with this and simply serve the request, implying a configured local domain. When the ProxyDomain directive is used and the server is configured for proxy service, Apache can return + href="#proxyrequests">configured for proxy service, Apache httpd can return a redirect response and send the client to the correct, fully qualified, server address. This is the preferred method since the user's bookmark files will then contain fully qualified hosts.

    @@ -350,7 +350,7 @@ response ProxyBadHeader IsError server configvirtual host -Available in Apache 2.0.44 and later +Available in Apache HTTP Server 2.0.44 and later

    The ProxyBadHeader directive determines the @@ -400,7 +400,7 @@ request server configvirtual host directory -Available in Apache 2.0.31 and later. Usable in directory +Available in Apache HTTP Server 2.0.31 and later. Usable in directory context in 2.3.3 and later. @@ -424,7 +424,7 @@ context in 2.3.3 and later. -

    This allows or prevents Apache from functioning as a forward proxy +

    This allows or prevents Apache httpd from functioning as a forward proxy server. (Setting ProxyRequests to Off does not disable use of the ProxyPass directive.)

    @@ -509,7 +509,7 @@ expressions >key=value [key=value ...]] directory -BalancerMember is only available in Apache 2.2 +BalancerMember is only available in Apache HTTP Server 2.2 and later.

    This directive adds a member to a load balancing group. It could be used @@ -533,7 +533,7 @@ expressions ProxySet url key=value [key=value ...] directory -ProxySet is only available in Apache 2.2 +ProxySet is only available in Apache HTTP Server 2.2 and later.

    This directive is used as an alternate method of setting any of the @@ -640,7 +640,7 @@ expressions general ProxyPass directive.

    -

    As of Apache 2.1, the ability to use pooled connections to a backend +

    As of Apache HTTP Server 2.1, the ability to use pooled connections to a backend server is available. Using the key=value parameters it is possible to tune this connection pooling. The default for a Hard Maximum for the number of connections is the number of threads per @@ -651,7 +651,7 @@ expressions

    Setting min will determine how many connections will always be open to the backend server. Upto the Soft Maximum or smax number of connections will be created on demand. Any connections above - smax are subject to a time to live or ttl. Apache + smax are subject to a time to live or ttl. Apache httpd will never create more than the Hard Maximum or max connections to the backend server.

    @@ -674,7 +674,7 @@ expressions for the number of connections is the number of threads per process in the active MPM. In the Prefork MPM, this is always 1, while with the Worker MPM it is controlled by the ThreadsPerChild. - Apache will never create more than the Hard Maximum connections + Apache httpd will never create more than the Hard Maximum connections to the backend server. smax max @@ -686,13 +686,13 @@ expressions - If set this will be the maximum time to wait for a free connection in the connection pool, in milliseconds. If there are no free - connections in the pool the Apache will return SERVER_BUSY + connections in the pool the Apache httpd will return SERVER_BUSY status to the client. connectiontimeout timeout Connect timeout in seconds. - The number of seconds Apache waits for the creation of a connection to + The number of seconds Apache httpd waits for the creation of a connection to the backend to complete. By adding a postfix of ms the timeout can be also set in milliseconds. @@ -701,7 +701,8 @@ expressions This parameter should be used when you want to force mod_proxy to immediately close a connection to the backend after being used, and thus, disable its persistent connection and pool for that backend. - This helps in various situations where a firewall between Apache and + This helps in various situations where a firewall between Apache + httpd and the backend server (regardless of protocol) tends to silently drop connections or when backends themselves may be under round- robin DNS. To disable connection pooling reuse, @@ -730,7 +731,7 @@ expressions keepalive Off This parameter should be used when you have a firewall between your - Apache and the backend server, who tend to drop inactive connections. + Apache httpd and the backend server, who tend to drop inactive connections. This flag will tell the Operating System to send KEEP_ALIVE messages on inactive connections (interval depends on global OS settings, generally 120ms), and thus prevent the firewall to drop the connection. @@ -777,7 +778,7 @@ expressions 60 Connection pool worker retry timeout in seconds. If the connection pool worker to the backend server is in the error state, - Apache will not forward any requests to that server until the timeout + Apache httpd will not forward any requests to that server until the timeout expires. This enables to shut down the backend server for maintenance, and bring it back online later. A value of 0 means always retry workers in an error state with no timeout. @@ -800,12 +801,12 @@ expressions timeout ProxyTimeout Connection timeout in seconds. - The number of seconds Apache waits for data sent by / to the backend. + The number of seconds Apache httpd waits for data sent by / to the backend. ttl - Time To Live for the inactive connections above the - smax connections in seconds. Apache will close all + smax connections in seconds. Apache httpd will close all connections that has not been used inside that time period. @@ -977,15 +978,15 @@ proxied server -

    This directive lets Apache adjust the URL in the Location, +

    This directive lets Apache httpd adjust the URL in the Location, Content-Location and URI headers on HTTP - redirect responses. This is essential when Apache is used as a + redirect responses. This is essential when Apache httpd is used as a reverse proxy (or gateway) to avoid by-passing the reverse proxy because of HTTP redirects on the backend servers which stay behind the reverse proxy.

    Only the HTTP response headers specifically mentioned above - will be rewritten. Apache will not rewrite other response + will be rewritten. Apache httpd will not rewrite other response headers, nor will it rewrite URL references inside HTML pages. This means that if the proxied content contains absolute URL references, they will by-pass the proxy. A third-party module @@ -1013,7 +1014,7 @@ proxied server (the functionality ProxyPass provides here). It also takes care of redirects the server backend.example.com sends: when http://backend.example.com/bar is redirected by him to - http://backend.example.com/quux Apache adjusts this to + http://backend.example.com/quux Apache httpd adjusts this to http://example.com/mirror/foo/quux before forwarding the HTTP redirect response to the client. Note that the hostname used for constructing the URL is chosen in respect to the setting of the ProxyMaxForwards -1 server configvirtual host -Available in Apache 2.0 and later; +Available in Apache HTTP Server 2.0 and later; default behaviour changed in 2.2.7/2.3 @@ -1181,7 +1182,7 @@ through

    Note that setting ProxyMaxForwards is a violation of the HTTP/1.1 protocol (RFC2616), which forbids a Proxy setting Max-Forwards if the Client didn't set it. - Earlier Apache versions would always set it. A negative + Earlier Apache httpd versions would always set it. A negative ProxyMaxForwards value, including the default -1, gives you protocol-compliant behaviour, but may leave you open to loops.

    @@ -1197,7 +1198,7 @@ directly -

    This directive is only useful for Apache proxy servers within +

    This directive is only useful for Apache httpd proxy servers within intranets. The NoProxy directive specifies a list of subnets, IP addresses, hosts and/or domains, separated by spaces. A request to a host which matches one or more of these is @@ -1298,7 +1299,7 @@ directly Note

    In many situations, it is more effective to specify an IPAddr in place of a Hostname since a - DNS lookup can be avoided. Name resolution in Apache can take a remarkable + DNS lookup can be avoided. Name resolution in Apache httpd can take a remarkable deal of time when the connection to the name server uses a slow PPP link.

    Hostname comparisons are done without regard to the case, @@ -1319,7 +1320,7 @@ directly Value of Timeout server configvirtual host -Available in Apache 2.0.31 and later +Available in Apache HTTP Server 2.0.31 and later

    This directive allows a user to specifiy a timeout on proxy requests. @@ -1337,7 +1338,7 @@ directly -

    This directive is only useful for Apache proxy servers within +

    This directive is only useful for Apache httpd proxy servers within intranets. The ProxyDomain directive specifies the default domain which the apache proxy server will belong to. If a request to a host without a domain name is encountered, a redirection @@ -1377,7 +1378,7 @@ header for proxied requests Via: header line added for the current host.

  • If set to Full, each generated Via: header - line will additionally have the Apache server version shown as a + line will additionally have the Apache httpd server version shown as a Via: comment field.
  • If set to Block, every proxy request will have all its