From 78d66dc68a908262432af21e2b6bf7e57650e04a Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Sat, 11 Feb 2023 17:40:05 -0500 Subject: [PATCH] docs: note that https:443 is now supported --- docs/networking/proxies/haproxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/networking/proxies/haproxy.md b/docs/networking/proxies/haproxy.md index bf2291d1a..8de8fbc59 100644 --- a/docs/networking/proxies/haproxy.md +++ b/docs/networking/proxies/haproxy.md @@ -25,7 +25,7 @@ The Haproxy plugin has specific rules for routing requests: - Haproxy integration is exposed via docker labels attached to containers. Changes in labels require either app deploys or rebuilds. - While Haproxy will respect labels associated with other containers, only `web` containers have Haproxy labels injected by the plugin. -- Only `http:80` port mappings are supported at this time. +- Only `http:80` and `https:443` port mappings are supported at this time. - Requests are routed as soon as the container is running and passing healthchecks. ### Switching to Haproxy