From dd533e4405182e3f1a1186434eb6d9a227e6b3ba Mon Sep 17 00:00:00 2001
From: rusty-snake <41237666+rusty-snake@users.noreply.github.com>
Date: Sat, 7 Jan 2023 16:55:07 +0000
Subject: [PATCH] =?UTF-8?q?Update=20Service=20Discovery=20example=20for=20?=
 =?UTF-8?q?Caddy=20=E2=80=A6?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

… in  reverse_proxy_configuration.rst

While the rewrite rules should work I guess, they still trigger a warning
on the admin page. Using 301 redirects make the warning go away.

Signed-off-by: rusty-snake <41237666+rusty-snake@users.noreply.github.com>
---
 .../configuration_server/reverse_proxy_configuration.rst      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/admin_manual/configuration_server/reverse_proxy_configuration.rst b/admin_manual/configuration_server/reverse_proxy_configuration.rst
index 531a9885a..535020a9c 100644
--- a/admin_manual/configuration_server/reverse_proxy_configuration.rst
+++ b/admin_manual/configuration_server/reverse_proxy_configuration.rst
@@ -128,8 +128,8 @@ Caddy
 ::
 
     subdomain.example.com {
-        rewrite /.well-known/carddav /remote.php/dav
-        rewrite /.well-known/caldav /remote.php/dav
+        redir /.well-known/carddav /remote.php/dav 301
+        redir /.well-known/caldav /remote.php/dav 301
 
         reverse_proxy {$NEXTCLOUD_HOST:localhost}
     }