Cyberduck Mountain Duck CLI

Changes between Version 72 and Version 73 of help/en/howto/dav


Ignore:
Timestamp:
Apr 27, 2021 7:38:36 AM (7 weeks ago)
Author:
svogt
Comment:

Edit Tabs and References

Legend:

Unmodified
Added
Removed
Modified
  • help/en/howto/dav

    v72 v73  
    66
    77== Providers ==
    8 Settings specific to service providers. Use the provided [https://trac.cyberduck.io/wiki/help/en/howto/connection#ConnectionProfiles connection profiles].
     8Settings are specific to service providers. Use the provided [wiki:help/en/howto/protocols#ConnectionProfiles connection profiles].
    99 * [wiki:help/en/howto/nextcloud Nextcloud]
    1010 * [wiki:help/en/howto/owncloud ownCloud]
     
    1515== Supported Authentication Methods ==
    1616=== HTTP Basic Authentiation ===
    17 Basic Authentication should only be used when using secured connection over TLS (HTTPS).
     17Basic Authentication should only be used when using a secured connection over TLS (HTTPS).
    1818
    1919=== HTTP Digest Authentication ===
     
    4545If the certificate is not trusted by the system, you are asked to make an exception if you still want to connect to the site that cannot be verified. This failure during certificate trust verification is most often the case when the certificate is invalid either
    4646 * Because the hostname does not match the common name in the certificate. You will get the error message ''You might be connecting to a server that is pretending to be…''.
    47  * The certificate is self signed or signed by a root authority not trusted in the system.
     47 * The certificate is self-signed or signed by a root authority not trusted in the system.
    4848 * The certificate is expired.
    4949
    50 You can temporarily or permanently allow to connect nevertheless by choosing ''Continue''. To remember your choice, select ''Always Trust…''.
     50You can temporarily or permanently allow connecting nevertheless by choosing ''Continue''. To remember your choice, select ''Always Trust…''.
    5151
    5252== Metadata ==
     
    5454
    5555== Locks ==
    56  * '''Cyberduck''' Files are not locked when [wiki:help/en/howto/edit editing] with Cyberduck.
    57  * '''Mountain Duck''' supports locking using `LOCK` and `UNLOCK` methods when opening documents for editing. Refer to [wiki:help/en/howto/mount/locking File Locking].
     56{{{#!html
     57<ul class="nav nav-tabs">
     58    <li class="active"><a href="#tabpanel-cyberduck-1" data-toggle="tab">Cyberduck</a></li>
     59    <li><a href="#tabpanel-mountainduck-1" data-toggle="tab">Mountain Duck</a></li>
     60</ul>
     61}}}
     62{{{#!div class="tab-content"
     63
     64{{{#!div class="tab-pane active" id="tabpanel-cyberduck-1"
     65
     66Files aren't locked when [wiki:help/en/howto/edit editing] with Cyberduck.
     67
     68}}}
     69
     70{{{#!div class="tab-pane" id="tabpanel-mountainduck-1"
     71
     72Mountain Duck supports locking using `LOCK` and `UNLOCK` methods when opening documents for editing. Refer to [wiki:help/en/howto/mount/locking File Locking].
     73
     74}}}
     75}}}
     76
    5877
    5978== Distribution (CDN) ==
     
    7695=== Interoperability failure `Handshake alert: unrecognized_name`  ===
    7796
    78 The virtual host setup by the hosting provider is most possibly misconfigured. It must accept TLS connections with SNI (Server Name Indication) extension (RFC 4366). The hostname must match the common name in the server certificate. In Apache ''httpd'' configurations, add a `ServerAlias` configuration directive with the hostname you use to connect.
     97The virtual host set up by the hosting provider is most possibly misconfigured. It must accept TLS connections with SNI (Server Name Indication) extension (RFC 4366). The hostname must match the common name in the server certificate. In Apache ''httpd'' configurations, add a `ServerAlias` configuration directive with the hostname you use to connect.
    7998
    80 You can verify the wrong server setup with running `openssl` with server name indication (SNI) enabled.
     99You can verify the wrong server setup by running `openssl` with server name indication (SNI) enabled.
    81100
    82101{{{
     
    90109}}}
    91110
    92 during the handshake if there is a configuration problem.
     111during the handshake, if there is a configuration problem.
    93112
    94113See also #7908.
     
    99118
    100119=== Socket timeout with GZIP content encoding ===
    101 Some servers (cPanel) have invalid return GZIP encoded content. This error may not bee seen with other clients that do not enable content compression. An invalid HTTP response status line is sent and the content size does not match the content length set. As a workaround, you can disable support for content compression. Set the [wiki:help/en/howto/preferences#Hiddenconfigurationoptions hidden option] `http.compression.enable` to `false`.
     120Some servers (cPanel) have invalid return GZIP encoded content. This error may not be seen with other clients that do not enable content compression. An invalid HTTP response status line is sent and the content size does not match the content length set. As a workaround, you can disable support for content compression. Set the [wiki:help/en/howto/preferences#Hiddenconfigurationoptions hidden option] `http.compression.enable` to `false`.
    102121
    103122=== Require Directive in Apache HTTPD ===
    104123The `Require` directive in Apache HTTPD tests whether an authenticated user is authorized according to a particular authorization provider and the specified restrictions. You should configure it to return a 403 HTTP status code when authorization fails using the `AuthzSendForbiddenOnFailure` directive. Refer to [https://httpd.apache.org/docs/current/mod/mod_authz_core.html#authzsendforbiddenonfailure mod_authz_core].
    105124
    106  If authentication succeeds but authorization fails, Apache HTTPD will respond with an HTTP response code of '401 UNAUTHORIZED' by default. This usually causes browsers to display the password dialogue to the user again, which is not wanted in all situations. AuthzSendForbiddenOnFailure allows to change the response code to '403 FORBIDDEN'.
     125 If authentication succeeds but authorization fails, Apache HTTPD will respond with an HTTP response code of '401 UNAUTHORIZED' by default. This usually causes browsers to display the password dialogue to the user again, which is not wanted in all situations. AuthzSendForbiddenOnFailure allows changing the response code to '403 FORBIDDEN'.
    107126
    108127