DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix typo stickyness to stickiness

Browse source
This commit is contained in:
lijianfeng1993 2018-02-07 15:38:45 +08:00
parent a30bf2154e
commit 954440409e
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/examples/affinity/cookie/README.md
View file

@ -4,7 +4,7 @@ This example demonstrates how to achieve session affinity using cookies
## Deployment ## 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| |Name|Description|Values|
| --- | --- | --- | | --- | --- | --- |
@ -55,7 +55,7 @@ Last-Modified: Tue, 24 Jan 2017 14:02:19 GMT
ETag: "58875e6b-264" ETag: "58875e6b-264"
Accept-Ranges: bytes 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. 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. If the user changes this cookie, NGINX creates a new one and redirect the user to another upstream.