| \n Name of the proxy. The name must be the fully qualified domain name (no scheme). If the proxy port differs from the default of 8080, it must be appended, separated by a colon. Examples: foo.bar:1704<\/i> or foo.bar<\/i><\/p>\n<\/td>\n<\/tr>\n<\/table>\n Only allowed in the system wide configuration file.<\/b><\/p>\n trust_ca_cert<\/b><\/p>\n Name of a certificate file in PEM format. The name of the file may be given as absolute path or as file name only. In the latter case the directories ~\/.davfs2\/certs<\/i> and \/etc\/davfs2\/certs<\/i> will be searched.
This option is useful when the certificate presented by the server cannot be verified using the system\u2019s data base of trusted certificate authorities (CA). The certificate file must contain the self-signed certificate of the top level CA in the chain of trust. It may be a self-signed server certificate (but see also trust_server_cert<\/b>). With this option the system\u2019s CA data base is ignored.
Note:<\/b> Even if the server\u2019s certificate is trusted that does not mean it is accepted. Additionally the certificate\u2019s date must be valid and either the CommonName or the SubjectAltName must match the host name of the server.<\/p>\n servercert<\/b><\/p>\n Same as trust_ca_cert<\/b> but badly named.
Deprecated<\/b><\/p>\n trust_server_cert<\/b><\/p>\n Name of a certificate file in PEM format. The name of the file may be given as absolute path or as file name only. In the latter case the directories ~\/.davfs2\/certs<\/i> and \/etc\/davfs2\/certs<\/i> will be searched.
Useful when the server\u2019s certificate can\u2019t be verified or is even invalid, but you know<\/b> that you can trust this certificate. When the server presents a certificate that is exactly equal to this one and when the server is able to authenticate against the public key contained in this certificate the connection will be established.
This is the preferred option for self signed server certificates.
No other ways to verify the certificate will be tried and the certificate will not be checked for validity.<\/p>\n clientcert<\/b><\/p>\n Name of a certificate in PKCS#12 format that will be used to authenticate with the server. The name of the file may be given as absolute path or as file name only. In the latter case the directories ~\/.davfs2\/certs\/private<\/i> and \/etc\/davfs2\/certs\/private<\/i> will be searched.
Warning:<\/b> If the client certificate is issued by an intermediary CA and not by a top level CA then the TLS-specification requires the client to send the complete chain of certificates (without the top level CA-certificate). davfs2 only sends the client certificate. To work around this bug the server must store and trust the complete chain of CA-certificates down to the one CA that isssued the client certificate.<\/p>\n secrets<\/b><\/p>\n Name of a file that holds the credentials for servers and the proxy, and passwords to decrypt the client certificate. The name must be an absolute path. The file must be read and writable by the owner only (mode 600).
Default: ~\/.davfs2\/secrets
Only allowed in the user configuration file.<\/b> The system wide secrets file is always \/etc\/davfs2\/secrets<\/i>.<\/p>\n ask_auth<\/b><\/p>\n Ask the user interactively for credentials and passwords if not found in the secretsfile. Ask the user if a servercert cannot be verified. 0 = no, 1 = yes.
Default: 1<\/p>\n use_locks<\/b><\/p>\n Whether to lock files on the server when they are opened for writing. 0 = no, 1 = yes.
Default: 1<\/p>\n lock_owner<\/b><\/p>\n A string send to the server to identify the owner of a lock. If a WebDAV resource is used at the same time by different clients using the same credentials, different values for lock_owner should be chosen.
Default: the username from the credentials<\/p>\n lock_timeout<\/b><\/p>\n How long in seconds locks should be valid, before the server removes them. The server may ignore this and set its own timeout value.
Default: 1800<\/p>\n lock_refresh<\/b><\/p>\n That many seconds before the lock times out, mount.davfs<\/b> will try to refresh the lock. The value should be substantially greater than delay_upload<\/b>.
Default: 60<\/p>\n use_expect100<\/b><\/p>\n To avoid uploading big files that will be refused by the server, mount.davfs<\/b> uses the header expect: 100\u2212continue<\/i> to get the o.k. from the server before uploading. Not all servers understand this. 0 = no, 1 = yes.
Default: 0<\/p>\n if_match_bug<\/b><\/p>\n Some servers do not handle If-Match and If-None-Match-headers correctly. This otion tells mount.davfs<\/b> to use HEAD instead of thes headers. 0 = no, 1 = yes.
Default: 0<\/p>\n drop_weak_etags<\/b><\/p>\n Popular servers send a weak etag whenever they are not able to calculate a strong one. This weak etag will never be valid, but after one second it is silently turned into a strong, valid etag. With this flag set to 1, mount.davfs<\/b> will never use this weak etags. If the flag is 0, the weakness indicator will be removed and the etag is assumed to be strong. There is some danger of the Lost-Update-Problem with this. But it is minimized when using locks.
You should turn this on, when you can\u2019t use locks and there is the danger of concurrent access to the same resource. In this case the etag is not used at all and the resource cannot be cached.
0 = no, 1 = yes.
Default: 0<\/p>\n n_cookies<\/b><\/p>\n Some servers will only work when they are allowed to set a cookie and this cookie is returned in subsequent requests. This option sets the number of cookies you are willing to accept and include in subsequent requests. davfs2 will only care for the name and the value of the cookie and ignore all of the possible attributes.
Default: 0<\/p>\n precheck<\/b><\/p>\n If option if_match_bug<\/b> is set: use HEAD-requests to check for existence or modification of a file to avoid unintended overwriting what somebody else changed. Has no effect if option if_match_bug<\/b> is 0. You should only set it 0, if there is no concurrent access to the server. 0 = no, 1 = yes.
Default: 1<\/p>\n ignore_dav_header<\/b><\/p>\n Some servers send wrong information about their capabilities in the DAV-header. In this case the header should be ignored.
Default: 0<\/p>\n use_compression<\/b><\/p>\n Use gzip-compression for downloading files, if supported by the server. Uploads will still be uncompressed.
Default: 0<\/p>\n min_propset<\/b><\/p>\n Some servers are reported to significantly slow down when the Etag and Last-Modified properties are requested. This option will reduce the set of WebDAV-properties requested from the server to the minimal set. Don\u2019t use it if your file system is used for reading and writing. Without Etag or Last-Modified davfs2 will not be able to check for changes on the server which may result in unnecessary downloads and lost updates. This option will also effectively disable caching of files because files in the cache can\u2019t be reused.
Default: 0<\/p>\n follow_redirect<\/b><\/p>\n If the server redirects a GET-request to a different resource (maybe on a different server) then follow this redirection.
Currently there are some restrictions: all redirects are treated as temporary redirects; if the new server requires authentication then the same credentials are use as for the original server; if the connection is over TLS the server certificate will be checked against the trusted CAs known by the system; user configured server certificates and client certificates are not used for the new server.
Default: 0<\/p>\n sharepoint_href_bug<\/b><\/p>\n SharePoint does not properly encode UTF8-characters within the href-element. Because of this some files are invisible because the href-element violates the rules. Neon 0.31 and newer has a workaround for this SharePoint bug. This option will activate this workaround.
Default: 0<\/p>\n server_charset<\/b><\/p>\n When extracting file names from the path component of the URL, mount.davfs<\/b> will assume they are encoded using this character set and translate file names to the local character set. This is not<\/b> about encoding of file contents and not<\/b> about HTTP escaping rules.
There is no means in HTTP to know the character encoding of the path component. There may be even different encodings within the same path, as the encoding of file names is often defined by the clients that created them. Nowadays it is best to use only UTF\u22128 encoding and to do no conversion. If you are not sure that all clients understand UTF\u22128, restrict file names to pure us\u2212ascii. Never use characters in file names, that may have a special function on some operating systems (like \/, : and ).
Default: no character set conversion<\/p>\n connect_timeout<\/b><\/p>\n When creating a TCP connection to the server mount.davfs<\/b> will wait that many seconds for an answer before assuming an error. If a value of \u20190\u2019 is used then no explicit timeout handling is set and the connect call will only timeout as dictated by the TCP stack.
This parameter only takes effect if the version of neon in use (neon version > 0.26) and the OS support non-blocking I\/O.
Default: 10<\/p>\n read_timeout<\/b><\/p>\n How long in seconds mount.davfs<\/b> will wait for an answer from the server before assuming an error.
Default: 30<\/p>\n |