You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2022. It is now read-only.
Sometimes the current health checks (TCP) are not enough. The current generated health checks for HAProxy is:
http: check
https: check ssl verify none
One example that won't work with the above simple healthchecks is when a specified origin is using https and resolves to loadbalancers that won't respond to TLS connections without SNI (for example CloudFront).
Sometimes the current health checks (TCP) are not enough. The current generated health checks for HAProxy is:
check
check ssl verify none
One example that won't work with the above simple healthchecks is when a specified origin is using https and resolves to loadbalancers that won't respond to TLS connections without SNI (for example CloudFront).
I propose that we use the existing format used for the internal ORM health check between HAProxy and Varnish (https://github.com/SVT/orm/blob/master/docs/syntax_reference.md#custom_internal_healthcheck), and extend it to support the health check customizations we need.
We could add something similar to the examples below to https://github.com/SVT/orm/blob/master/docs/syntax_reference.md#origin_object :
When not setting healthcheck, we need to agree on some sane default for HAProxy (inspired by #7). For example:
check
check ssl check-sni <domain> verify required
The text was updated successfully, but these errors were encountered: