Documentation typo

[Cedric Jeanneret]

Hello again !

just checking the page, I fumble into another typo in the title of a section:
"SSL certifcate chains" should be "SSL certificate chains", I guess ;)

Cheers,

C.

On Wed, 10 Nov 2010 15:33:14 +0300
Igor Sysoev <igor at sysoev.ru> wrote:

> On Wed, Nov 10, 2010 at 03:26:41PM +0300, Maxim Dounin wrote:
> 
> > Hello!
> > 
> > On Wed, Nov 10, 2010 at 02:42:41PM +0300, Igor Sysoev wrote:
> > 
> > > On Wed, Nov 10, 2010 at 06:33:57AM -0500, Merlin Meyer-Mitchell wrote:
> > > 
> > > > On page
> > > > 
> > > > http://nginx.org/en/docs/http/configuring_https_servers.html
> > > > 
> > > > It clearly should say "Since OpenSSL 0.9.8j this option..." or perhaps "...supports SNI since 0.8.9f version...". &nbsp;As is it's logically inconsistent. &nbsp;See extract:
> > > > 
> > > > "
> > > > In order to use SNI in nginx, it must be supported in both the OpenSSL library with which the nginx binary has been built as well as the library to which it is being dynamically linked at run time. OpenSSL supports SNI since 0.9.8f version if it was built with config option “--enable-tlsext”. Since OpenSSL 0.8.9j this option is enabled by default. If nginx was built with SNI support, then nginx will show this when run with the “-V” switch:
> > > > "
> > > 
> > > OpenSSL supports SNI starting with 0.9.8f version. Nowever, you have to
> > > enable this capability during OpenSSL building using the option
> > > "--enable-tlsext". Since OpenSSL 0.8.9j this option is enabled by default.
> > 
> > - 0.8.9j
> > + 0.9.8j
> 
> Thank you, I have fixed the current edition.
> 
> 


-- 
Cédric Jeanneret                 |  System Administrator
021 619 10 32                    |  Camptocamp SA
cedric.jeanneret at camptocamp.com  |  PSE-A / EPFL
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://nginx.org/pipermail/nginx/attachments/20101110/7a99c718/attachment.pgp>