Directive can have multiple meanings. Each variant is separated with horizontal line


[edit] ssl_engine

Syntax: ssl_engine device
Default:
Context: main
Reference: ssl_engine


Here you can set your preferred openssl engine if any available. You can figure out which one do you have with the commandline tool: openssl engine -t

For example:

$ openssl engine -t
(cryptodev) BSD cryptodev engine
  [ available ] 
(dynamic) Dynamic engine loading support
  [ unavailable ] 

Module: CoreModule

[edit] ssl_engine

syntax: ssl_engine

This allows specifying the OpenSSL engine to use, like PadLock, for example. It requires a recent version of OpenSSL. To verify if the OpenSSL version installed in your platform supports this, issue the command:

openssl engine

On a Debian testing with OpenSSL version 0.9.8o from 01 Jun 2010 it returns:

$ openssl engine
(padlock) VIA PadLock (no-RNG, no-ACE)
(dynamic) Dynamic engine loading support

[edit] Built-in variables

Module ngx_http_ssl_module supports the following built-in variables:

[edit] Nonstandard error codes

This module supports several nonstandard error codes which can be used for debugging with the aid of directive error_page:

Debugging is done after the request is completely "disassembled" and it's components are accessible via variables such as $request_uri, $uri, $arg and more.

[edit] References


Module: HttpSslModule