comparison xml/en/docs/http/configuring_https_servers.xml @ 782:2ceaef0e84a1

Added a phrase about wildcard certificates into the English version of configuring_https_servers.xml that first appeared in Russian translation. While here, paraphrased one nearby sentence.
author Ruslan Ermilov <ru@nginx.com>
date Tue, 11 Dec 2012 13:36:37 +0000
parents e1579b244800
children b95a6d779c89
comparison
equal deleted inserted replaced
781:1ff2580fd5de 782:2ceaef0e84a1
6 <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd"> 6 <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd">
7 7
8 <article name="Configuring HTTPS servers" 8 <article name="Configuring HTTPS servers"
9 link="/en/docs/http/configuring_https_servers.html" 9 link="/en/docs/http/configuring_https_servers.html"
10 lang="en" 10 lang="en"
11 rev="3" 11 rev="4"
12 author="Igor Sysoev" 12 author="Igor Sysoev"
13 editor="Brian Mercer"> 13 editor="Brian Mercer">
14 14
15 <section> 15 <section>
16 16
311 311
312 <section id="certificate_with_several_names" 312 <section id="certificate_with_several_names"
313 name="An SSL certificate with several names"> 313 name="An SSL certificate with several names">
314 314
315 <para> 315 <para>
316 There are other ways to share a single IP address between several 316 There are other ways that allow to share a single IP address
317 HTTPS servers, however, all of them have drawbacks. 317 between several HTTPS servers.
318 However, all of them have their drawbacks.
318 One way is to use a certificate with several names in 319 One way is to use a certificate with several names in
319 the SubjectAltName certificate field, for example, 320 the SubjectAltName certificate field, for example,
320 <literal>www.example.com</literal> and <literal>www.example.org</literal>. 321 <literal>www.example.com</literal> and <literal>www.example.org</literal>.
321 However, the SubjectAltName field length is limited. 322 However, the SubjectAltName field length is limited.
322 </para> 323 </para>
323 324
324 <para> 325 <para>
325 Another way is to use a certificate with a wildcard name, for example, 326 Another way is to use a certificate with a wildcard name, for example,
326 <literal>*.example.org</literal>. 327 <literal>*.example.org</literal>.
328 A wildcard certificate secures all subdomains of the specified domain,
329 but only on one level.
327 This certificate matches <literal>www.example.org</literal>, but does not match 330 This certificate matches <literal>www.example.org</literal>, but does not match
328 <literal>example.org</literal> and <literal>www.sub.example.org</literal>. 331 <literal>example.org</literal> and <literal>www.sub.example.org</literal>.
329 These two methods can also be combined. 332 These two methods can also be combined.
330 A certificate may contain exact and wildcard names in the 333 A certificate may contain exact and wildcard names in the
331 SubjectAltName field, for example, 334 SubjectAltName field, for example,