nginx-site: xml/en/docs/http/ngx_http_proxy

comparison xml/en/docs/http/ngx_http_proxy_module.xml @ 294:9f5ee1c6fca5

Use consistent wording.

author	Ruslan Ermilov <ru@nginx.com>
date	Thu, 29 Dec 2011 06:48:26 +0000
parents	7142ddd2764c
children	94c8df379088

comparison

equal deleted inserted replaced

-:34246e706f48
+:9f5ee1c6fca5
 <context>http</context>
 <context>server</context>
 <context>location</context>
 <para>
-Defines conditions under which the answer will not be taken from a cache.
+Defines conditions under which the response will not be taken from a cache.
 If at least one value of the string parameters is not empty and is not
-equal to “0” then the answer will not be taken from the cache:
+equal to “0” then the response will not be taken from the cache:
 <example>
 proxy_cache_bypass $cookie_nocache $arg_nocache$arg_comment;
 proxy_cache_bypass $http_pragma    $http_authorization;
 </example>
 Can be used along with the <link id="proxy_no_cache"/> directive.
 </example>
 then only 200, 301, and 302 responses are cached.
 </para>
 <para>
-In addition, it can be specified to cache any answers using the
+In addition, it can be specified to cache any responses using the
 <literal>any</literal> parameter:
 <example>
 proxy_cache_valid 200 302 10m;
 proxy_cache_valid 301      1h;
 proxy_cache_valid any      1m;
 <header>Server</header>, <header>X-Pad</header>, and
 <header>X-Accel-...</header> from the response of a proxied
 server to a client.
 The <literal>proxy_hide_header</literal> directive sets additional fields
 that will not be passed.
-If, on the contrary, the passing of fields needs to be enabled,
+If, on the contrary, the passing of fields needs to be permitted,
 the <link id="proxy_pass_header"/> directive can be used.
 </para>
 </directive>
 <context>location</context>
 <para>
 Determines should the connection with a proxied server be
 closed if a client closes a connection without waiting
-for an answer.
+for a response.
 </para>
 </directive>
 <context>http</context>
 <context>server</context>
 <context>location</context>
 <para>
-Disables processing of some response header fields from the proxied server.
+Disables processing of certain response header fields from the proxied server.
 The following fields can be ignored: <header>X-Accel-Redirect</header>,
 <header>X-Accel-Expires</header>, <header>X-Accel-Limit-Rate</header> (1.1.6),
 <header>X-Accel-Buffering</header> (1.1.6),
 <header>X-Accel-Charset</header> (1.1.6), <header>Expires</header>,
 <header>Cache-Control</header>, and <header>Set-Cookie</header> (0.8.44).
 <context>http</context>
 <context>server</context>
 <context>location</context>
 <para>
-Defines conditions under which the answer will not be saved to a cache.
+Defines conditions under which the response will not be saved to a cache.
 If at least one value of the string parameters is not empty and is not
-equal to “0” then the answer will not be saved:
+equal to “0” then the response will not be saved:
 <example>
 proxy_no_cache $cookie_nocache $arg_nocache$arg_comment;
 proxy_no_cache $http_pragma    $http_authorization;
 </example>
 Can be used along with the <link id="proxy_cache_bypass"/> directive.
 here a path is specified after the word “<literal>unix</literal>”
 and enclosed in two colons.
 </para>
 <para>
-If a domain name maps to several addresses, all of them will be
+If a domain name resolves to several addresses, all of them will be
 used in a round-robin fashion.
 In addition, an address can be specified as a
 <link doc="ngx_http_upstream_module.xml">server group</link>.
 </para>

Mercurial > hg > nginx-site

comparison xml/en/docs/http/ngx_http_proxy_module.xml @ 294:9f5ee1c6fca5