diff options
Diffstat (limited to 'i18n/en/README_POST_INSTALL_EN')
| -rw-r--r-- | i18n/en/README_POST_INSTALL_EN | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/i18n/en/README_POST_INSTALL_EN b/i18n/en/README_POST_INSTALL_EN index 840bf6b..1d61b03 100644 --- a/i18n/en/README_POST_INSTALL_EN +++ b/i18n/en/README_POST_INSTALL_EN @@ -5,8 +5,8 @@ <p>In the <strong>Security & setup warnings</strong> section it is likely that some messages are shown, on how to improve the setup. The items mentioned cannot be done by the Nextcloud integration for UCS, instead the admin needs to decide whether actions should be taken.</p> <h3>"Strict-Transport-Security" HTTP header</h3> <p>To harden the service against man-in-the-middle attacks, this mechanism can be enabled. The SSL termination happens on the reverse proxy, which typically is an Apache2 web server on the host. The configuration for the domain(s) Nextcloud is running on would need to be extended with an HTTP header. Applying the changes affects all services running within this domain.</p> -<p>This <a href="https://docs.nextcloud.com/server/21/admin_manual/installation/harden_server.html#enable-http-strict-transport-security">documentation page explains how to configure HSTS</a>. The <strong>includeSubDomains</strong> is necessary.</p> +<p>This <a href="https://docs.nextcloud.com/server/22/admin_manual/installation/harden_server.html#enable-http-strict-transport-security">documentation page explains how to configure HSTS</a>. The <strong>includeSubDomains</strong> is necessary.</p> <h3>Not able to resolve "/.well-known/caldav|carddav"</h3> -<p>Discovery of addressbook and calendar services can be made easier for such clients, by providing well-known URLs that redirect to the actual location of that service. This check tests whether the top-level domain has the given URLs present. Again, to resolve this, the web server configuration of the host needs to be adjusted, <a href="https://docs.nextcloud.com/server/21/admin_manual/issues/general_troubleshooting.html#service-discovery">according to this documentation</a>.<p> +<p>Discovery of addressbook and calendar services can be made easier for such clients, by providing well-known URLs that redirect to the actual location of that service. This check tests whether the top-level domain has the given URLs present. Again, to resolve this, the web server configuration of the host needs to be adjusted, <a href="https://docs.nextcloud.com/server/22/admin_manual/issues/general_troubleshooting.html#service-discovery">according to this documentation</a>.<p> <p>It is only possible to link to one service provider on a domain. Having the URLs present is not crucial for a working Nextcloud setup, but improves the convenience for some end users.</p> <p>The check was introduced within the Nextcloud 13 series. Thus in the earlier version the hint was not shown.</p> |