1davfs2.conf(5) 1.5.4 davfs2.conf(5)
2
6 davfs2.conf - Configuration file for mount.davfs
7
11 There is a system wide configuration file /etc/davfs2/davfs2.conf and
12 user configuration files ~/.davfs2/davfs2.conf. When mount.davfs is
13 invoked by root, only the system wide configuration file is read. When
14 invoked by an ordinary user, the user configuration file is read in
15 addition. Settings from the user configuration file will take prece‐
16 dence over the system wide configuration.
17 The configuration file consists of lines where each line contains a
20 keyword value pair. Keyword and value are seperated by spaces and/or
21 tabs.
22 The file may contain sections that are for one specific mount point
25 only. Such a section starts with a line, that contains the full path
26 of the mount point enclosed in square brackets. The section ends at the
27 start of the next section or the end of file. Options that shall apply
28 to all mounted file system must come before the first sections. Options
29 given in a mount specific section will have precedence.
30
34 kernel_fs coda
35 proxy foo.bar:8080
36 use_locks 0
37 [/media/dav]
38 use_locks 1
39 [/home/otto/mywebspace]
40 gui_optimize 1
41 All mounted davfs2 file systems will use the coda kernel file system
44 and the proxy foo.bar. All davfs2 file systems expect /media/dav will
45 disable the use of the locks. /home/otto/mywebspace will use the
46 gui_optimize option.
47
50 Lines that only contain spaces and tabs (empty lines) are ignored.
51 # indicates a comment. The rest of the line is ignored.
54 \ is the escape character.
57 "" is used for quotation.
60 If a value contains one of the special characters space, tab, #, \, or
63 ", this character must be escaped by a preceding \. Use ’\ ’ instead of
64 ’ ’, ’\#’ instead of ’#’, ’\\’ instead of ’\’ and ’\"’ instead of ’"’.
65 Values containing spaces, tabs or # may instead be enclosed in double
68 quotes. But " and ’ must be escaped even within double quotes. If the
69 starting line of a section is enclosed in double quotes, the square
70 brakets must be within the quotes (like "[/home/otto/with space]").
71 Boolean option values (yes/no) must be given as numerical value. 0 for
74 no, 1 for yes.
75
80 dav_user
81 When invoked by root the mount.davfs daemon will run as this
82 user. Value must be given as name, not as numerical id.
83 Default: davfs2
84 Only allowed in the system wide configuration file.
85 dav_group
88 The group of the running mount.davfs daemon. Ordinary users must
89 be member of this group in order to mount a davfs2 file system.
90 Value must be given as name, not as numerical id.
91 Default: davfs2
92 Only allowed in the system wide configuration file.
93 kernel_fs
96 Which kernel file system to use, to integrate into the virtual
97 file system. Possible values are fuse and coda.
98 Default: fuse
99 buf_size
102 Size in KiByte of the buffer used to communicate with the kernel
103 file system. Only usefull with fuse, where read and write oper‐
104 ations may profit from a larger buffer.
105 Default: 16
106
110 use_proxy
111 Whether to use a proxy to connect to the WebDAV server. 0 = no,
112 1 = yes. If no proxy is defined in the configration file or the
113 environment variables https_proxy, http_proxy and all_proxy,
114 this option has no effect.
115 Default: 1
116 Only allowed in the system wide configuration file.
117 proxy Name of the proxy. The name must be the fully qualified domain
120 name (no scheme). If the proxy port differs from the default of
121 8080, it must be appended, seperated by a colon. Examples:
122 foo.bar:1704 or foo.bar
123 Only allowed in the system wide configuration file.
124 trust_ca_cert
127 Name of a certificate file in PEM format. The name of the file
128 may be given as absolute path or as file name only. In the lat‐
129 ter case the directories ~/.davfs2/certs and /etc/davfs2/certs
130 will be searched.
131 This option is useful when the certificate presented by the
132 server cannot be verified using the system's data base of
133 trusted certificate authorities (CA). The certificate file must
134 contain the self-signed certificate of the top level CA in the
135 chain of trust. It may be a self-signed server certificate (but
136 see also trust_server_cert). With this option the system's CA
137 data base is ignored.
138 Note: Even if the server's certificate is trusted that does not
139 mean it is accepted. Additionally the certificate's date must be
140 valid and either the CommonName or the SubjectAltName must match
141 the host name of the server.
142 servercert
145 Same as trust_ca_cert but badly named.
146 Deprecated
147 trust_server_cert
150 Name of a certificate file in PEM format. The name of the file
151 may be given as absolute path or as file name only. In the lat‐
152 ter case the directories ~/.davfs2/certs and /etc/davfs2/certs
153 will be searched.
154 Usefull when the server's certificate can't be verified or is
155 even invalid, but you know that you can trust this certificate.
156 When the server presents a certificate that is exactly equal to
157 this one and when the server is able to authenticate against the
158 public key contained in this certificate the connection will be
159 established.
160 This is the preferred option for self signed server certifi‐
161 cates.
162 No other ways to verify the certificate will be tried and the
163 certificate will not be checked for validity.
164 clientcert
167 Name of a certificate in PKCS#12 format that will be used to
168 authenticate with the server. The name of the file may be given
169 as absolute path or as file name only. In the latter case the
170 directories ~/.davfs2/certs/private and /etc/davfs2/certs/pri‐
171 vate will be searched.
172 secrets
175 Name of a file that holds the credentials for servers and the
176 proxy, and passwords to decrypt the client certificate. The name
177 must be an absolute path. The file must be read and writable by
178 the owner only (mode 600).
179 Default: ~/.davfs2/secrets
180 Only allowed in the user configuration file. The system wide
181 secrets file is allways /etc/davfs2/secrets.
182 ask_auth
185 Ask the user interactively for credentials and passwords if not
186 found in the secretsfile. Ask the user if a servercert cannot be
187 verified. 0 = no, 1 = yes.
188 Default: 1
189 use_locks
192 Whether to lock files on the server when they are opened for
193 writing. 0 = no, 1 = yes.
194 Default: 1
195 lock_owner
198 A string send to the server to identify the owner of a lock. If
199 a WebDAV resource is used at the same time by different clients
200 using the same credentials, different values for lock_owner
201 should be choosen.
202 Default: the username from the credentials
203 lock_timeout
206 How long in seconds locks should be valid, before the server
207 removes them. The server may ignore this and set its own time‐
208 out value.
209 Default: 1800
210 lock_refresh
213 That many seconds before the lock times out, mount.davfs will
214 try to refresh the lock. The value should be substantially
215 greater than delay_upload.
216 Default: 60
217 use_expect100
220 To avoid uploading big files that will be refused by the
221 server, mount.davfs uses the header expect: 100-continue to get
222 the o.k. from the server before uploading. Not all servers
223 understand this. 0 = no, 1 = yes.
224 Default: 0
225 if_match_bug
228 Some servers do not handle If-Match and If-None-Match-headers
229 correctly. This otion tells mount.davfs to use HEAD instead of
230 thes headers. 0 = no, 1 = yes.
231 Default: 0
232 drop_weak_etags
235 Popular servers send a weak etag whenever they are not able to
236 calculate a strong one. This weak etag will never be valid, but
237 after one second it is silently turned into a strong, valid
238 etag. With this flag set to 1, mount.davfs will never use this
239 weak etags. If the flag is 0, the weakness indicator will be
240 removed and the etag is assumed to be strong. There is some dan‐
241 ger of the Lost-Update-Problem with this. But it is minimized
242 when using locks.
243 You should turn this on, when you can't use locks and there is
244 the danger of concurrent access to the same resource. In this
245 case the etag is not used at all and the resource cannot be
246 cached.
247 0 = no, 1 = yes.
248 Default: 0
249 n_cookies
252 Some servers will only work when they are allowed to set a
253 cookie and this cookie is returned in subsequent requests. This
254 option sets the number of cookies you are willing to accept and
255 include in subsequent requests. davfs2 will only care for the
256 name and the value of the cookie and ignore all of the possible
257 attributes.
258 Default: 0
259 precheck
262 If option if_match_bug is set: use HEAD-requests to check for
263 existence or modification of a file to avoid unintended over‐
264 writing what somebody else changed. Has no effect if option
265 if_match_bug is 0. You should only set it 0, if there is no con‐
266 current access to the server. 0 = no, 1 = yes.
267 Default: 1
268 ignore_dav_header
271 Some servers send wrong information about their capabilities in
272 the DAV-header. In this case the header should be ignored.
273 Default: 0
274 use_compression
277 Use gzip-compression for downloading files, if supported by the
278 server. Uploads will still be uncompressed.
279 Default: 0
280 min_propset
283 Some servers are reported to significantly slow down when the
284 Etag and Last-Modified properties are requested. This option
285 will reduce the set of WebDAV-properties requested from the
286 server to the minimal set. Don't use it if your file system is
287 used for reading and writing. Without Etag or Last-Modified
288 davfs2 will not be able to check for changes on the server which
289 may result in unnecessary downloads and lost updates. This
290 option will also effectively disable caching of files because
291 files in the cache can't be reused.
292 Default: 0
293 follow_redirect
296 If the server redirects a GET-request to a different resource
297 (maybe on a different server) then follow this redirection.
298 Currently there are some restrictions: all redirects are treated
299 as temporary redirects; if the new server requires authentica‐
300 tion then the same credentials are use as for the original
301 server; if the connection is over TLS the server certificate
302 will be checked against the trusted CAs known by the system;
303 user configured server certificates and client certificates are
304 not used for the new server.
305 Default: 0
306 server_charset
309 When extracting file names from the path component of the URL,
310 mount.davfs will assume they are encoded using this character
311 set and translate file names to the local character set. This is
312 not about encoding of file contents and not about HTTP escaping
313 rules.
314 There is no means in HTTP to know the character encoding of the
315 path component. There may be even different encodings within the
316 same path, as the encoding of file names is often defined by the
317 clients that created them. Nowadays it is best to use only
318 UTF-8 encoding and to do no conversion. If you are not sure that
319 all clients understand UTF-8, restrict file names to pure
320 us-ascii. Never use characters in file names, that may have a
321 special function on some operating systems (like /, : and \).
322 Default: no character set conversion
323 connect_timeout
326 When creating a TCP connection to the server mount.davfs will
327 wait that many seconds for an answer before assuming an error.
328 If a value of '0' is used then no explicit timeout handling is
329 set and the connect call will only timeout as dictated by the
330 TCP stack.
331 This parameter only takes effect if the version of neon in use
332 (neon version > 0.26) and the OS support non-blocking I/O.
333 Default: 10
334 read_timeout
337 How long in seconds mount.davfs will wait for an answer from the
338 server before assuming an error.
339 Default: 30
340 retry When mount.davfs can not reach the server it will try again
343 after retry seconds. For subsequent retries the interval will be
344 increased up to max_retry seconds.
345 Default: 30
346 max_retry
349 Maximum value of the retry interval.
350 Default: 300
351 max_upload_attempts
354 When uploading a changed file fails temporarily mount.davfs will
355 retry with increasing intervals, but not more often than this.
356 With a bad connection this will cause additional traffic. To
357 reduce traffic caused by unsuccessful attempts option
358 use_expect100 can be set. But please test it. Most proxies and
359 some servers don't support this header.
360 Default: 15
361 add_header
364 Your server might expect special headers to do what you want.
365 Different from other options, this one takes two values: the
366 name of the header and its value. Some ASP-backends to IIS seem
367 to require the Microsoft specific header "Translate: F". You can
368 add it like this:
369 add_header Translate F
370 mount.davfs will add header "Translate: F" on all requests.
371 This option is cumulative. You can enter more than one
372 add_header option and all of them will be added. Also add_header
373 options from /etc/davfs2/davfs2.conf and ~/.davfs2/davfs2.conf
374 are merged.
375
379 backup_dir
380 Each mounted davfs2 file system has a directory to store backups
381 of files that could not be stored back to the server. This sets
382 the name of this directory. You should regularly check this
383 directory.
384 Default: lost+found
385 cache_dir
388 The directory where mount.davfs will store cached files. For
389 every mount point a subdirectory will be created.
390 In the systemwide configuration file this will set the system
391 wide cache, used by root. In a users configuration file it will
392 set the cache used by this user.
393 Defaults: /var/cache/davfs2 and ~/.davfs2/cache
394 cache_size
397 The amount of disk space in MiByte that may be used. mount.davfs
398 will always take enough space to cache open files, ignoring this
399 value if necessary.
400 Default: 50
401 table_size
404 mount.davfs maintains a hash table with an entry for each known
405 file or directory. This gives the number of entries in this ta‐
406 ble. For large file systems (more than some hundreds of files)
407 increasing this number may speed up file operations. The value
408 should be a power of 2.
409 Default: 1024
410 dir_refresh
413 After mount.davfs has got information about files in a directory
414 it considers it valid for this time in seconds. Note: This does
415 not affect opening of files and reading a directory by an appli‐
416 cation.
417 Default: 60
418 file_refresh
421 When a file or directory is opened by an application,
422 mount.davfs will first check the server for a newer version. But
423 some applications do open calls on the same file in short
424 sequence. To avoid unecessary traffic mount.davfs will wait that
425 many seconds before it send a new request for the same informa‐
426 tion.
427 Default: 1
428 delay_upload
431 When a file that has been changed is closed, mount.davfs will
432 wait that many seconds before it will upload it to the server.
433 This will avoid uploading of temporary files that will be
434 removed immediately after closing. If you need the files to
435 appear on the server immediately after closing, set this option
436 to 0.
437 Default: 10
438 gui_optimize
441 When a file is opened, mount.davfs will have to check the server
442 whether there is a newer version. Graphical User Interfaces tend
443 to open just any file, slowing down things dramatically for
444 large directories. With this option mount.davfs will try to get
445 this information from all files in a directory with one PROPFIND
446 request. 0 = no, 1 = yes.
447 Default: 0
448 minimize_mem
451 davfs2 holds information about files and directories in the
452 working memory. It will stay there as long as the file system is
453 mounted and the file is not deleted. By this memory usage by
454 davfs2 will grow over time and may slow down davfs2. With this
455 option set to 1 davfs2 will regularly clean the memory from
456 information that has not be used for some time. 0 = no, 1 =
457 yes.
458 Warning: Most file attributes are only maintained locally
459 because there is no corresponding WebDAV property. So if users
460 change attributes (owner, group, access bits) locally this
461 changes will be lost and attribute values will be reset to the
462 default values.
463 Default: 0
464
468 debug Send debug messages to the syslog daemon. The value tells what
469 kind of information shall be logged. The messages are send with
470 facility LOG_DAEMON and priority LOG_DEBUG. It depends from the
471 configuration of the syslog daemon where the messages will go
472 (propably /var/log/messages, /var/log/syslog or /var/log/dae‐
473 mon.log). Whether HTTP related debug messages are available
474 depends on your neon library.
475 Unlike other options, this option is cumulative. If there are
476 several debug entries with different values, all of them will be
477 applied. Also debug options from /etc/davfs2/davfs2.conf and
478 ~/.davfs2/davfs2.conf are merged.
479 Note: Debug messages let the log-files grow quickly. Never use
480 this option in normal operation of mount.davfs.
481 Default: no debugging messages
482 Recognized values:
484 config Command line and configuration options.
486 kernel Upcalls from the kernel file system.
488 cache Cache operations like adding and removing nodes.
490 http HTTP headers.
492 xml Parsing of the XML-body of WebDAV-requests.
494 httpauth
496 Negotiation of authentication.
497 locks Information about locks.
499 ssl TLS/SSL related stuff like certificates.
501 httpbody
503 Complete body of HTTP-responses.
504 secrets
506 Also print confidential information, which is usually
507 omitted or obscured.
508 most Includes config, kernel, cache and http.
510
514 This man page was written by by Werner Baumann <werner.baumann@online‐
515 home.de>.
516
520 http://savannah.nongnu.org/projects/davfs2
521
525 mount.davfs(8), umount.davfs(8), mount(8), umount(8), fstab(5)
526davfs2 2014-06-09 davfs2.conf(5)