From: Christophe Jaillet Date: Mon, 19 Apr 2021 12:55:51 +0000 (+0000) Subject: Fix some typos X-Git-Tag: 2.4.47~14 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2d72e33dc636052c6e2dd122391608b6985c92dd;p=thirdparty%2Fapache%2Fhttpd.git Fix some typos + remove ome leading/trailing space to synch with trunk [skip ci] git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1888962 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml index 7b731a8ebbe..64fe9caaa61 100644 --- a/docs/manual/mod/mod_proxy.xml +++ b/docs/manual/mod/mod_proxy.xml @@ -215,7 +215,7 @@ ProxyVia On for a reverse proxy:

- ProxyPass "/example" "http://backend.example.com" connectiontimeout=5 timeout=30 +ProxyPass "/example" "http://backend.example.com" connectiontimeout=5 timeout=30

This will create a worker associated with the origin server URL @@ -224,7 +224,7 @@ ProxyVia On via the ProxySet directive:

- ProxySet "http://backend.example.com" connectiontimeout=5 timeout=30 +ProxySet "http://backend.example.com" connectiontimeout=5 timeout=30

or alternatively using Proxy @@ -473,7 +473,7 @@ ProxyPass "/examples" "http://backend.example.com/examples" timeout=10 other request headers.

Note: If you need to specify custom request headers to be - added to the forwarded request, use the + added to the forwarded request, use the RequestHeader directive.

@@ -513,14 +513,14 @@ ProxyPass "/examples" "http://backend.example.com/examples" timeout=10 Differences from the Location configuration section -

A backend URL matches the configuration section if it begins with the +

A backend URL matches the configuration section if it begins with the the wildcard-url string, even if the last path segment in the - directive only matches a prefix of the backend URL. For example, - <Proxy "http://example.com/foo"> matches all of - http://example.com/foo, http://example.com/foo/bar, and + directive only matches a prefix of the backend URL. For example, + <Proxy "http://example.com/foo"> matches all of + http://example.com/foo, http://example.com/foo/bar, and http://example.com/foobar. The matching of the final URL differs from the behavior of the Location section, which for purposes of this note + >Location section, which for purposes of this note treats the final path component as if it ended in a slash.

For more control over the matching, see ProxyMatch.

@@ -1030,7 +1030,7 @@ ProxyPass "/mirror/foo/i" "!" Example - ProxyPass "/example" "http://backend.example.com" max=20 ttl=120 retry=300 +ProxyPass "/example" "http://backend.example.com" max=20 ttl=120 retry=300 @@ -1292,7 +1292,7 @@ ProxyPass "/mirror/foo/i" "!" stickysessionsep "." Sets the separation symbol in the session cookie. Some backend application servers - do not use the '.' as the symbol. For example, the Oracle Weblogic server uses + do not use the '.' as the symbol. For example, the Oracle Weblogic server uses '!'. The correct symbol can be set using this option. The setting of 'Off' signifies that no symbol is used. @@ -1397,8 +1397,8 @@ ProxyPass "/" "balancer://hotcluster/" But this may be incompatible with some backends, particularly those that make use of PATH_INFO. The optional nocanon keyword suppresses this and passes the URL path "raw" to the - backend. Note that this keyword may affect the security of your backend, - as it removes the normal limited protection against URL-based attacks + backend. Note that this keyword may affect the security of your backend, + as it removes the normal limited protection against URL-based attacks provided by the proxy.

Normally, mod_proxy will include the query string when @@ -1451,14 +1451,14 @@ ProxyPassReverse "/mirror/foo/" "https://backend.example.com/" matches, the server will substitute any parenthesized matches into the given string and use it as a new url.

- Note: This directive cannot be used within a + Note: This directive cannot be used within a <Directory> context.

Suppose the local server has address http://example.com/; then

- ProxyPassMatch "^/(.*\.gif)$" "http://backend.example.com/$1" +ProxyPassMatch "^/(.*\.gif)$" "http://backend.example.com/$1"

will cause a local request for @@ -1469,13 +1469,13 @@ ProxyPassReverse "/mirror/foo/" "https://backend.example.com/" substitutions (as well as after). This limits the matches you can use. For instance, if we had used

- ProxyPassMatch "^(/.*\.gif)$" "http://backend.example.com:8000$1" +ProxyPassMatch "^(/.*\.gif)$" "http://backend.example.com:8000$1"

in our previous example, it would fail with a syntax error at server startup. This is a bug (PR 46665 in the ASF bugzilla), and the workaround is to reformulate the match:

- ProxyPassMatch "^/(.*\.gif)$" "http://backend.example.com:8000/$1" +ProxyPassMatch "^/(.*\.gif)$" "http://backend.example.com:8000/$1"

The ! directive is useful in situations where you don't want @@ -1552,7 +1552,7 @@ ProxyPassReverseCookiePath "/" "/mirror/foo/"

will not only cause a local request for the http://example.com/mirror/foo/bar to be internally converted into a proxy request to http://backend.example.com/bar - (the functionality which ProxyPass provides here). + (the functionality which ProxyPass provides here). It also takes care of redirects which the server backend.example.com sends when redirecting http://backend.example.com/bar to http://backend.example.com/quux . Apache httpd adjusts this to @@ -1626,7 +1626,7 @@ reverse proxy. This directive rewrites the path string in internal-path, the cookie path will be replaced with public-path.

-In the example given with +In the example given with ProxyPassReverse, the directive:

@@ -1733,7 +1733,7 @@ connections ProxyMaxForwards -Maximium number of proxies that a request can be forwarded +Maximum number of proxies that a request can be forwarded through ProxyMaxForwards number ProxyMaxForwards -1 @@ -1898,7 +1898,7 @@ NoProxy ".example.com" "192.168.112.0/21" -

This directive allows a user to specifiy a timeout on proxy requests. +

This directive allows a user to specify a timeout on proxy requests. This is useful when you have a slow/buggy appserver which hangs, and you would rather just return a timeout and fail gracefully instead of waiting however long it takes the server to return.