From f0e90213bb5db2afada27e4368c8d0235c0317bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Cl=C3=A9ment=20OUDOT?= <clement@oodo.net>
Date: Thu, 4 Mar 2021 15:13:30 +0100
Subject: [PATCH] (doc) How to overwrite protocol in NextCloud

---
 doc/sources/admin/applications/nextcloud.rst | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/doc/sources/admin/applications/nextcloud.rst b/doc/sources/admin/applications/nextcloud.rst
index 4603f9ae5..e0b7cfe39 100644
--- a/doc/sources/admin/applications/nextcloud.rst
+++ b/doc/sources/admin/applications/nextcloud.rst
@@ -30,14 +30,13 @@ software <https://docs.nextcloud.com/server/10/admin_manual/installation/index.h
     If your NextCloud is behind a proxy (thus having a private
     IP), metadata generated by NextCloud won't work.
 
-    Consider changing the configuration of NextCloud to force the domain, in
+    Consider changing the configuration of NextCloud to force the domain and the protocol, in
     **$nextcloudrootwww/config/config.php**, add the following:
 
     .. code:: php
 
        'overwritehost' => 'nextcloud.example.com',
-
-
+       'overwriteprotocol' => 'https',
 
 You also need to enable the "SAML authentication" plugin in your
 NextCloud. <code> + Apps -> Not enabled -> SAML authentication</code>