Mercurial > hg > nginx-site
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
293:34246e706f48 | 294:9f5ee1c6fca5 |
---|---|
122 <context>http</context> | 122 <context>http</context> |
123 <context>server</context> | 123 <context>server</context> |
124 <context>location</context> | 124 <context>location</context> |
125 | 125 |
126 <para> | 126 <para> |
127 Defines conditions under which the answer will not be taken from a cache. | 127 Defines conditions under which the response will not be taken from a cache. |
128 If at least one value of the string parameters is not empty and is not | 128 If at least one value of the string parameters is not empty and is not |
129 equal to “0” then the answer will not be taken from the cache: | 129 equal to “0” then the response will not be taken from the cache: |
130 <example> | 130 <example> |
131 proxy_cache_bypass $cookie_nocache $arg_nocache$arg_comment; | 131 proxy_cache_bypass $cookie_nocache $arg_nocache$arg_comment; |
132 proxy_cache_bypass $http_pragma $http_authorization; | 132 proxy_cache_bypass $http_pragma $http_authorization; |
133 </example> | 133 </example> |
134 Can be used along with the <link id="proxy_no_cache"/> directive. | 134 Can be used along with the <link id="proxy_no_cache"/> directive. |
285 </example> | 285 </example> |
286 then only 200, 301, and 302 responses are cached. | 286 then only 200, 301, and 302 responses are cached. |
287 </para> | 287 </para> |
288 | 288 |
289 <para> | 289 <para> |
290 In addition, it can be specified to cache any answers using the | 290 In addition, it can be specified to cache any responses using the |
291 <literal>any</literal> parameter: | 291 <literal>any</literal> parameter: |
292 <example> | 292 <example> |
293 proxy_cache_valid 200 302 10m; | 293 proxy_cache_valid 200 302 10m; |
294 proxy_cache_valid 301 1h; | 294 proxy_cache_valid 301 1h; |
295 proxy_cache_valid any 1m; | 295 proxy_cache_valid any 1m; |
327 <header>Server</header>, <header>X-Pad</header>, and | 327 <header>Server</header>, <header>X-Pad</header>, and |
328 <header>X-Accel-...</header> from the response of a proxied | 328 <header>X-Accel-...</header> from the response of a proxied |
329 server to a client. | 329 server to a client. |
330 The <literal>proxy_hide_header</literal> directive sets additional fields | 330 The <literal>proxy_hide_header</literal> directive sets additional fields |
331 that will not be passed. | 331 that will not be passed. |
332 If, on the contrary, the passing of fields needs to be enabled, | 332 If, on the contrary, the passing of fields needs to be permitted, |
333 the <link id="proxy_pass_header"/> directive can be used. | 333 the <link id="proxy_pass_header"/> directive can be used. |
334 </para> | 334 </para> |
335 | 335 |
336 </directive> | 336 </directive> |
337 | 337 |
344 <context>location</context> | 344 <context>location</context> |
345 | 345 |
346 <para> | 346 <para> |
347 Determines should the connection with a proxied server be | 347 Determines should the connection with a proxied server be |
348 closed if a client closes a connection without waiting | 348 closed if a client closes a connection without waiting |
349 for an answer. | 349 for a response. |
350 </para> | 350 </para> |
351 | 351 |
352 </directive> | 352 </directive> |
353 | 353 |
354 | 354 |
358 <context>http</context> | 358 <context>http</context> |
359 <context>server</context> | 359 <context>server</context> |
360 <context>location</context> | 360 <context>location</context> |
361 | 361 |
362 <para> | 362 <para> |
363 Disables processing of some response header fields from the proxied server. | 363 Disables processing of certain response header fields from the proxied server. |
364 The following fields can be ignored: <header>X-Accel-Redirect</header>, | 364 The following fields can be ignored: <header>X-Accel-Redirect</header>, |
365 <header>X-Accel-Expires</header>, <header>X-Accel-Limit-Rate</header> (1.1.6), | 365 <header>X-Accel-Expires</header>, <header>X-Accel-Limit-Rate</header> (1.1.6), |
366 <header>X-Accel-Buffering</header> (1.1.6), | 366 <header>X-Accel-Buffering</header> (1.1.6), |
367 <header>X-Accel-Charset</header> (1.1.6), <header>Expires</header>, | 367 <header>X-Accel-Charset</header> (1.1.6), <header>Expires</header>, |
368 <header>Cache-Control</header>, and <header>Set-Cookie</header> (0.8.44). | 368 <header>Cache-Control</header>, and <header>Set-Cookie</header> (0.8.44). |
456 <context>http</context> | 456 <context>http</context> |
457 <context>server</context> | 457 <context>server</context> |
458 <context>location</context> | 458 <context>location</context> |
459 | 459 |
460 <para> | 460 <para> |
461 Defines conditions under which the answer will not be saved to a cache. | 461 Defines conditions under which the response will not be saved to a cache. |
462 If at least one value of the string parameters is not empty and is not | 462 If at least one value of the string parameters is not empty and is not |
463 equal to “0” then the answer will not be saved: | 463 equal to “0” then the response will not be saved: |
464 <example> | 464 <example> |
465 proxy_no_cache $cookie_nocache $arg_nocache$arg_comment; | 465 proxy_no_cache $cookie_nocache $arg_nocache$arg_comment; |
466 proxy_no_cache $http_pragma $http_authorization; | 466 proxy_no_cache $http_pragma $http_authorization; |
467 </example> | 467 </example> |
468 Can be used along with the <link id="proxy_cache_bypass"/> directive. | 468 Can be used along with the <link id="proxy_cache_bypass"/> directive. |
492 here a path is specified after the word “<literal>unix</literal>” | 492 here a path is specified after the word “<literal>unix</literal>” |
493 and enclosed in two colons. | 493 and enclosed in two colons. |
494 </para> | 494 </para> |
495 | 495 |
496 <para> | 496 <para> |
497 If a domain name maps to several addresses, all of them will be | 497 If a domain name resolves to several addresses, all of them will be |
498 used in a round-robin fashion. | 498 used in a round-robin fashion. |
499 In addition, an address can be specified as a | 499 In addition, an address can be specified as a |
500 <link doc="ngx_http_upstream_module.xml">server group</link>. | 500 <link doc="ngx_http_upstream_module.xml">server group</link>. |
501 </para> | 501 </para> |
502 | 502 |