summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Lange <code@nerdmind.de>2017-02-25 00:11:16 +0100
committerThomas Lange <code@nerdmind.de>2017-02-25 00:11:16 +0100
commit603cd7a3c9745f3f9f7fb234a392a0446a2be4ba (patch)
tree6f9252c217a91dee23b4376ee4f417858f59b78a
parentcb83c296fe252b99f77a5fc7f1a10bab60bc14e5 (diff)
downloadwiki-603cd7a3c9745f3f9f7fb234a392a0446a2be4ba.tar.gz
wiki-603cd7a3c9745f3f9f7fb234a392a0446a2be4ba.tar.xz
wiki-603cd7a3c9745f3f9f7fb234a392a0446a2be4ba.zip
Better explanation of the ETag settings.
-rw-r--r--Configuration.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Configuration.md b/Configuration.md
index 19af41b..f028850 100644
--- a/Configuration.md
+++ b/Configuration.md
@@ -6,7 +6,7 @@ This is the core language which will be used. A corresponding language file **mu
* `CORE.LANGUAGE`: [string: `'en'`]
## ETag configuration
-If this parameter is set to `TRUE`, the system will generate an `ETag` header which includes the timestamps of the last published items and sends them to the client. The client will cache this header and sends them with each further request in the request header. If the ETag header is not modified (which means that no new items was published), the application exit and returns the `304 Not Modified` response header.
+If this parameter is set to `TRUE`, the system will generate an `ETag` header which includes a hash of the configuration and the timestamps of the last published items and sends them to the client. The client will cache this header and sends them with each further request in the request header to the application. If the hash which the appplication now again creates is not the same as the one from the request header (which means that no new items was published), the application exit and returns the `304 Not Modified` response header.
* `CORE.SEND_304`: [boolean: `TRUE`|`FALSE`]