summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRémy Coutable <remy@rymai.me>2017-03-15 09:01:16 +0100
committerRémy Coutable <remy@rymai.me>2017-03-15 09:01:16 +0100
commit028bca7bc5b56787d6dd1f53188fb1dbca235a0c (patch)
treea634e5bf7158098db354e320ab88047f567298ca
parent253b61d2a03fe04877cedb88260dbb69f59e7e89 (diff)
downloadgitlab-ce-fix-polling-doc.tar.gz
Fix typo in doc/development/polling.md: `If-None-Modified` -> `If-None-Match`fix-polling-doc
Signed-off-by: Rémy Coutable <remy@rymai.me>
-rw-r--r--doc/development/polling.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/polling.md b/doc/development/polling.md
index a086aca6697..a7f2962acf0 100644
--- a/doc/development/polling.md
+++ b/doc/development/polling.md
@@ -27,13 +27,13 @@ Instead you should use polling mechanism with ETag caching in Redis.
1. When a client makes a request we set the `ETag` response header to the value
from Redis.
1. The client caches the response (client-side caching) and sends the ETag as
- the `If-None-Modified` header with every subsequent request for the same
+ the `If-None-Match` header with every subsequent request for the same
resource.
-1. If the `If-None-Modified` header matches the current value in Redis we know
+1. If the `If-None-Match` header matches the current value in Redis we know
that the resource did not change so we can send 304 response immediately,
without querying the database at all. The client's browser will use the
cached response.
-1. If the `If-None-Modified` header does not match the current value in Redis
+1. If the `If-None-Match` header does not match the current value in Redis
we have to generate a new response, because the resource changed.
For more information see: