From a1ede0235dbfd6de82dd120f482e939f7485897b Mon Sep 17 00:00:00 2001
From: bt90 <btom1990@googlemail.com>
Date: Sun, 24 Jul 2022 14:22:32 +0200
Subject: [PATCH] Map 443/udp to allow HTTP3

---
 caddy/content.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/caddy/content.md b/caddy/content.md
index 6c802113f..9762a3445 100644
--- a/caddy/content.md
+++ b/caddy/content.md
@@ -49,7 +49,7 @@ $ docker run -d -p 80:80 \
 The default `Caddyfile` only listens to port `80`, and does not set up automatic TLS. However, if you have a domain name for your site, and its A/AAAA DNS records are properly pointed to this machine's public IP, then you can use this command to simply serve a site over HTTPS:
 
 ```console
-$ docker run -d -p 80:80 -p 443:443 \
+$ docker run -d -p 80:80 -p 443:443 -p 443:443/udp \
     -v /site:/srv \
     -v caddy_data:/data \
     -v caddy_config:/config \
@@ -123,6 +123,7 @@ services:
     ports:
       - "80:80"
       - "443:443"
+      - "443:443/udp"
     volumes:
       - $PWD/Caddyfile:/etc/caddy/Caddyfile
       - $PWD/site:/srv