hrm: callout sni forwards immediately

Signed-off-by: Trapier Marshall <trapier.marshall@docker.com>
This commit is contained in:
Trapier Marshall 2018-07-18 14:42:55 -04:00
parent 4286b1f8e9
commit 6fac75ad0f
2 changed files with 14 additions and 0 deletions

View File

@ -130,6 +130,13 @@ These keys are supported:
| sticky_sessions | no | cookie-name | Always route a user to the same service, using HTTP cookies. This option can't be used with HTTPS routes |
| redirect | no | http://domain-name, or sni://domain-name | Redirect incoming requests to another route using an HTTP 301 redirect |
> Known issue
>
> For `sni` (https) routes, HRM forwards to service tasks before any task
> health checks have passed. This may result in traffic loss if a task is not
> ready to serve traffic immediately after it is scheduled.
{: .important}
### Sticky sessions

View File

@ -152,6 +152,13 @@ These keys are supported:
| include_forwarded_for | no | true | If present, include the X-Forwarded-For header in requests |
> Known issue
>
> For `sni` (https) routes, HRM forwards to service tasks before any task
> health checks have passed. This may result in traffic loss if a task is not
> ready to serve traffic immediately after it is scheduled.
{: .important}
### Sticky sessions
You can use the `sticky_sessions` value to always route a user to the same