From e03d1293f9f7d0cb9f215a55190131f2b549ce21 Mon Sep 17 00:00:00 2001 From: Jianfeng Li Date: Wed, 7 Feb 2018 23:23:06 +0800 Subject: [PATCH] fix typo stickyness to stickiness (#2039) --- docs/examples/affinity/cookie/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/examples/affinity/cookie/README.md b/docs/examples/affinity/cookie/README.md index f93605d7e..4c17a4cc3 100644 --- a/docs/examples/affinity/cookie/README.md +++ b/docs/examples/affinity/cookie/README.md @@ -4,7 +4,7 @@ This example demonstrates how to achieve session affinity using cookies ## Deployment -Session stickyness is achieved through 3 annotations on the Ingress, as shown in the [example](ingress.yaml). +Session stickiness is achieved through 3 annotations on the Ingress, as shown in the [example](ingress.yaml). |Name|Description|Values| | --- | --- | --- | @@ -55,7 +55,7 @@ Last-Modified: Tue, 24 Jan 2017 14:02:19 GMT ETag: "58875e6b-264" Accept-Ranges: bytes ``` -In the example above, you can see a line containing the 'Set-Cookie: route' setting the right defined stickyness cookie. +In the example above, you can see a line containing the 'Set-Cookie: route' setting the right defined stickiness cookie. This cookie is created by NGINX containing the hash of the used upstream in that request. If the user changes this cookie, NGINX creates a new one and redirect the user to another upstream.