Changeset 444e6ed in mod_gnutls

Timestamp:

Oct 29, 2016, 7:00:04 PM (18 months ago)

Author:

Thomas Klute <thomas2.klute@…>

Branches:

debian/master, master, upstream

Children:

0cd8f3d

Parents:

ef107fd

git-author:

Thomas Klute <thomas2.klute@…> (10/29/16 18:55:57)

git-committer:

Thomas Klute <thomas2.klute@…> (10/29/16 19:00:04)

Message:

Fix documentation of GnuTLSCacheTimeout

GnuTLSCacheTimeout has nothing to do with the lifetime of TLS session
tickets, but it is used for OCSP responses if they do not contain a
nextUpdate field.

This commit also includes some minor rephrasing of other parts of the
session cache documentation.

File:

• doc/mod_gnutls_manual.mdwn (modified) (5 diffs)

doc/mod_gnutls_manual.mdwn

@@ -83 +83 @@
 `dbm` (Requires Berkeley DBM)
 :   Uses the default Berkeley DB backend of APR DBM to cache TLS
-    Sessions results.  The argument is a relative or absolute path to
+    Session data. The argument is a relative or absolute path to
     be used as the DBM Cache file. This is compatible with most
     operating systems, but needs the Apache Runtime to be compiled
@@ -89 +89 @@
 
 `gdbm`
-:   Uses the GDBM backend of APR DBM to cache TLS Sessions results.
+:   Uses the GDBM backend of APR DBM to cache TLS Session data.
 
     The argument is a relative or absolute path to be used as the DBM Cache
@@ -95 +95 @@
 
 `memcache`
-:   Uses a memcached server to cache the TLS Session.
+:   Uses memcached server(s) to cache TLS Session data.
 
     The argument is a space separated list of servers. If no port
@@ -118 +118 @@
 Context: server config
 
-Sets the timeout for TLS Session Cache entries expiration.  This
-directive is valid even if Session Tickets are used, and indicates the
-expiration time of the ticket in seconds.
+Sets the timeout for TLS Session Cache entries expiration. This value
+is also used for OCSP responses if they do not contain a `nextUpdate`
+time.
 
 ### GnuTLSSessionTickets
@@ -131 +131 @@
 Context: server config, virtual host
 
-To avoid storing data for TLS session resumption it is allowed to
-provide client with a ticket, to use on return. Tickets are an
+To avoid storing data for TLS session resumption the server can
+provide clients with tickets, to use on return. Tickets are an
 alternative to using a session cache, mostly used for busy servers
 with limited storage. For a pool of servers this option is not