Mercurial > hg > nginx-site
comparison xml/en/docs/http/ngx_http_charset_module.xml @ 966:95c3c3bbf1ce
Text review.
author | Egor Nikitin <yegor.nikitin@gmail.com> |
---|---|
date | Wed, 14 Aug 2013 12:03:41 +0400 |
parents | 417dc982362e |
children | b8f0362f61e5 |
comparison
equal
deleted
inserted
replaced
965:fadccc156188 | 966:95c3c3bbf1ce |
---|---|
83 In such a case, all possible values of a variable need to be present | 83 In such a case, all possible values of a variable need to be present |
84 in the configuration at least once in the form of the | 84 in the configuration at least once in the form of the |
85 <link id="charset_map"/>, <link id="charset"/>, or | 85 <link id="charset_map"/>, <link id="charset"/>, or |
86 <link id="source_charset"/> directives. | 86 <link id="source_charset"/> directives. |
87 For <literal>utf-8</literal>, <literal>windows-1251</literal>, and | 87 For <literal>utf-8</literal>, <literal>windows-1251</literal>, and |
88 <literal>koi8-r</literal> charsets it is sufficient to include the files | 88 <literal>koi8-r</literal> charsets, it is sufficient to include the files |
89 <path>conf/koi-win</path>, <path>conf/koi-utf</path>, and | 89 <path>conf/koi-win</path>, <path>conf/koi-utf</path>, and |
90 <path>conf/win-utf</path> into configuration. | 90 <path>conf/win-utf</path> into configuration. |
91 For other charsets, simply making a fictitious conversion table works, | 91 For other charsets, simply making a fictitious conversion table works, |
92 for example: | 92 for example: |
93 <example> | 93 <example> |
94 charset_map iso-8859-5 _ { } | 94 charset_map iso-8859-5 _ { } |
95 </example> | 95 </example> |
96 </para> | 96 </para> |
97 | 97 |
98 <para> | 98 <para> |
99 In addition, charset can also be set in the | 99 In addition, a charset can be set in the |
100 <header>X-Accel-Charset</header> response header field. | 100 <header>X-Accel-Charset</header> response header field. |
101 This ability can be disabled using the | 101 This capability can be disabled using the |
102 <link doc="ngx_http_proxy_module.xml" id="proxy_ignore_headers"/> | 102 <link doc="ngx_http_proxy_module.xml" id="proxy_ignore_headers"/> |
103 and | 103 and |
104 <link doc="ngx_http_fastcgi_module.xml" id="fastcgi_ignore_headers"/> | 104 <link doc="ngx_http_fastcgi_module.xml" id="fastcgi_ignore_headers"/> |
105 directives. | 105 directives. |
106 </para> | 106 </para> |
192 <context>server</context> | 192 <context>server</context> |
193 <context>location</context> | 193 <context>location</context> |
194 <context>if in location</context> | 194 <context>if in location</context> |
195 | 195 |
196 <para> | 196 <para> |
197 Determines if a conversion should be performed for answers | 197 Determines whether a conversion should be performed for answers |
198 received from a proxied or FastCGI server, | 198 received from a proxied or FastCGI server |
199 if the answers already carry a charset in the <header>Content-Type</header> | 199 when the answers already carry a charset in the <header>Content-Type</header> |
200 response header field. | 200 response header field. |
201 If conversion is enabled, a charset specified in the received | 201 If conversion is enabled, a charset specified in the received |
202 response is used as a source charset. | 202 response is used as a source charset. |
203 <note> | 203 <note> |
204 It should be noted that if a response was received in a subrequest | 204 It should be noted that if a response is received in a subrequest |
205 then conversion from the response charset to the main request charset | 205 then the conversion from the response charset to the main request charset |
206 is always performed regardless of the <literal>override_charset</literal> | 206 is always performed, regardless of the <literal>override_charset</literal> |
207 directive setting. | 207 directive setting. |
208 </note> | 208 </note> |
209 </para> | 209 </para> |
210 | 210 |
211 </directive> | 211 </directive> |