Mercurial > hg > nginx-site

comparison xml/en/docs/http/configuring_https_servers.xml @ 121:49443032011c

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Unified <section> syntax for "article" and "module" documents.
author Ruslan Ermilov <ru@nginx.com>
date Thu, 20 Oct 2011 20:27:51 +0000
parents a10bc0cb0a6a
children 7db449e89e92
comparison
equal deleted inserted replaced
120:da8bd4d2290f 121:49443032011c
64 </para> 64 </para>
65 65
66 </section> 66 </section>
67 67
68 68
69 <section name="optimization" title="HTTPS server optimization"> 69 <section id="optimization" name="HTTPS server optimization">
70 70
71 <para> 71 <para>
72 SSL operations consume extra CPU resources. 72 SSL operations consume extra CPU resources.
73 On multi-processor systems you should run several worker processes: 73 On multi-processor systems you should run several worker processes:
74 no less than the number of available CPU cores. 74 no less than the number of available CPU cores.
107 </para> 107 </para>
108 108
109 </section> 109 </section>
110 110
111 111
112 <section name="chains" title="SSL certificate chains"> 112 <section id="chains" name="SSL certificate chains">
113 113
114 <para> 114 <para>
115 Some browsers may complain about a certificate signed by a well-known 115 Some browsers may complain about a certificate signed by a well-known
116 certificate authority, while other browsers may accept the certificate 116 certificate authority, while other browsers may accept the certificate
117 without issues. 117 without issues.
204 </para> 204 </para>
205 205
206 </section> 206 </section>
207 207
208 208
209 <section name="single_http_https_server" title="A single HTTP/HTTPS server"> 209 <section id="single_http_https_server" name="A single HTTP/HTTPS server">
210 210
211 <para> 211 <para>
212 It is good practice to configure separate servers for HTTP and HTTPS 212 It is good practice to configure separate servers for HTTP and HTTPS
213 protocols from the very start. Although their functionalities currently 213 protocols from the very start. Although their functionalities currently
214 seem equal, this may change significantly in the future 214 seem equal, this may change significantly in the future
240 </para> 240 </para>
241 241
242 </section> 242 </section>
243 243
244 244
245 <section name="name_based_https_servers" title="Name-based HTTPS servers"> 245 <section id="name_based_https_servers" name="Name-based HTTPS servers">
246 246
247 <para> 247 <para>
248 A common issue arises when configuring two or more HTTPS servers 248 A common issue arises when configuring two or more HTTPS servers
249 listening on a single IP address: 249 listening on a single IP address:
250 250
298 </para> 298 </para>
299 299
300 </section> 300 </section>
301 301
302 302
303 <section name="certificate_with_several_names" 303 <section id="certificate_with_several_names"
304 title="A SSL certificate with several names"> 304 name="A SSL certificate with several names">
305 305
306 <para> 306 <para>
307 There are other ways to share a single IP address between several 307 There are other ways to share a single IP address between several
308 HTTPS servers, however, all of them have drawbacks. 308 HTTPS servers, however, all of them have drawbacks.
309 One way is to use a certificate with several names in 309 One way is to use a certificate with several names in
347 </para> 347 </para>
348 348
349 </section> 349 </section>
350 350
351 351
352 <section name="sni" title="Server Name Indication"> 352 <section id="sni" name="Server Name Indication">
353 353
354 <para> 354 <para>
355 A more generic solution for running several HTTPS servers on a single 355 A more generic solution for running several HTTPS servers on a single
356 IP address is 356 IP address is
357 <a href="http://en.wikipedia.org/wiki/Server_Name_Indication">TLSv1.1 357 <a href="http://en.wikipedia.org/wiki/Server_Name_Indication">TLSv1.1
415 </para> 415 </para>
416 416
417 </section> 417 </section>
418 418
419 419
420 <section name="compatibility" title="Compatibility"> 420 <section id="compatibility" name="Compatibility">
421 421
422 <para> 422 <para>
423 <list> 423 <list>
424 424
425 <item> 425 <item>