1davfs2.conf(5) 1.5.6 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 separated 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 except /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 useful with fuse, where read and write opera‐
104 tions 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, separated 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 Useful 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 Warning: If the client certificate is issued by an intermediary
173 CA and not by a top level CA then the TLS-specification requires
174 the client to send the complete chain of certificates (without
175 the top level CA-certificate). davfs2 only sends the client cer‐
176 tificate. To work around this bug the server must store and
177 trust the complete chain of CA-certificates down to the one CA
178 that isssued the client certificate.
179 secrets
182 Name of a file that holds the credentials for servers and the
183 proxy, and passwords to decrypt the client certificate. The name
184 must be an absolute path. The file must be read and writable by
185 the owner only (mode 600).
186 Default: ~/.davfs2/secrets
187 Only allowed in the user configuration file. The system wide
188 secrets file is always /etc/davfs2/secrets.
189 ask_auth
192 Ask the user interactively for credentials and passwords if not
193 found in the secretsfile. Ask the user if a servercert cannot be
194 verified. 0 = no, 1 = yes.
195 Default: 1
196 use_locks
199 Whether to lock files on the server when they are opened for
200 writing. 0 = no, 1 = yes.
201 Default: 1
202 lock_owner
205 A string send to the server to identify the owner of a lock. If
206 a WebDAV resource is used at the same time by different clients
207 using the same credentials, different values for lock_owner
208 should be chosen.
209 Default: the username from the credentials
210 lock_timeout
213 How long in seconds locks should be valid, before the server
214 removes them. The server may ignore this and set its own time‐
215 out value.
216 Default: 1800
217 lock_refresh
220 That many seconds before the lock times out, mount.davfs will
221 try to refresh the lock. The value should be substantially
222 greater than delay_upload.
223 Default: 60
224 use_expect100
227 To avoid uploading big files that will be refused by the
228 server, mount.davfs uses the header expect: 100-continue to get
229 the o.k. from the server before uploading. Not all servers
230 understand this. 0 = no, 1 = yes.
231 Default: 0
232 if_match_bug
235 Some servers do not handle If-Match and If-None-Match-headers
236 correctly. This otion tells mount.davfs to use HEAD instead of
237 thes headers. 0 = no, 1 = yes.
238 Default: 0
239 drop_weak_etags
242 Popular servers send a weak etag whenever they are not able to
243 calculate a strong one. This weak etag will never be valid, but
244 after one second it is silently turned into a strong, valid
245 etag. With this flag set to 1, mount.davfs will never use this
246 weak etags. If the flag is 0, the weakness indicator will be
247 removed and the etag is assumed to be strong. There is some dan‐
248 ger of the Lost-Update-Problem with this. But it is minimized
249 when using locks.
250 You should turn this on, when you can't use locks and there is
251 the danger of concurrent access to the same resource. In this
252 case the etag is not used at all and the resource cannot be
253 cached.
254 0 = no, 1 = yes.
255 Default: 0
256 n_cookies
259 Some servers will only work when they are allowed to set a
260 cookie and this cookie is returned in subsequent requests. This
261 option sets the number of cookies you are willing to accept and
262 include in subsequent requests. davfs2 will only care for the
263 name and the value of the cookie and ignore all of the possible
264 attributes.
265 Default: 0
266 precheck
269 If option if_match_bug is set: use HEAD-requests to check for
270 existence or modification of a file to avoid unintended over‐
271 writing what somebody else changed. Has no effect if option
272 if_match_bug is 0. You should only set it 0, if there is no con‐
273 current access to the server. 0 = no, 1 = yes.
274 Default: 1
275 ignore_dav_header
278 Some servers send wrong information about their capabilities in
279 the DAV-header. In this case the header should be ignored.
280 Default: 0
281 use_compression
284 Use gzip-compression for downloading files, if supported by the
285 server. Uploads will still be uncompressed.
286 Default: 0
287 min_propset
290 Some servers are reported to significantly slow down when the
291 Etag and Last-Modified properties are requested. This option
292 will reduce the set of WebDAV-properties requested from the
293 server to the minimal set. Don't use it if your file system is
294 used for reading and writing. Without Etag or Last-Modified
295 davfs2 will not be able to check for changes on the server which
296 may result in unnecessary downloads and lost updates. This
297 option will also effectively disable caching of files because
298 files in the cache can't be reused.
299 Default: 0
300 follow_redirect
303 If the server redirects a GET-request to a different resource
304 (maybe on a different server) then follow this redirection.
305 Currently there are some restrictions: all redirects are treated
306 as temporary redirects; if the new server requires authentica‐
307 tion then the same credentials are use as for the original
308 server; if the connection is over TLS the server certificate
309 will be checked against the trusted CAs known by the system;
310 user configured server certificates and client certificates are
311 not used for the new server.
312 Default: 0
313 server_charset
316 When extracting file names from the path component of the URL,
317 mount.davfs will assume they are encoded using this character
318 set and translate file names to the local character set. This is
319 not about encoding of file contents and not about HTTP escaping
320 rules.
321 There is no means in HTTP to know the character encoding of the
322 path component. There may be even different encodings within the
323 same path, as the encoding of file names is often defined by the
324 clients that created them. Nowadays it is best to use only
325 UTF-8 encoding and to do no conversion. If you are not sure that
326 all clients understand UTF-8, restrict file names to pure
327 us-ascii. Never use characters in file names, that may have a
328 special function on some operating systems (like /, : and \).
329 Default: no character set conversion
330 connect_timeout
333 When creating a TCP connection to the server mount.davfs will
334 wait that many seconds for an answer before assuming an error.
335 If a value of '0' is used then no explicit timeout handling is
336 set and the connect call will only timeout as dictated by the
337 TCP stack.
338 This parameter only takes effect if the version of neon in use
339 (neon version > 0.26) and the OS support non-blocking I/O.
340 Default: 10
341 read_timeout
344 How long in seconds mount.davfs will wait for an answer from the
345 server before assuming an error.
346 Default: 30
347 retry When mount.davfs can not reach the server it will try again
350 after retry seconds. For subsequent retries the interval will be
351 increased up to max_retry seconds.
352 Default: 30
353 max_retry
356 Maximum value of the retry interval.
357 Default: 300
358 max_upload_attempts
361 When uploading a changed file fails temporarily mount.davfs will
362 retry with increasing intervals, but not more often than this.
363 With a bad connection this will cause additional traffic. To
364 reduce traffic caused by unsuccessful attempts option
365 use_expect100 can be set. But please test it. Most proxies and
366 some servers don't support this header.
367 Default: 15
368 add_header
371 Your server might expect special headers to do what you want.
372 Different from other options, this one takes two values: the
373 name of the header and its value. Some ASP-backends to IIS seem
374 to require the Microsoft specific header "Translate: F". You can
375 add it like this:
376 add_header Translate F
377 mount.davfs will add header "Translate: F" on all requests.
378 This option is cumulative. You can enter more than one
379 add_header option and all of them will be added. Also add_header
380 options from /etc/davfs2/davfs2.conf and ~/.davfs2/davfs2.conf
381 are merged.
382
386 backup_dir
387 Each mounted davfs2 file system has a directory to store backups
388 of files that could not be stored back to the server. This sets
389 the name of this directory. You should regularly check this
390 directory.
391 Default: lost+found
392 cache_dir
395 The directory where mount.davfs will store cached files. For
396 every mount point a subdirectory will be created.
397 In the systemwide configuration file this will set the system
398 wide cache, used by root. In a users configuration file it will
399 set the cache used by this user.
400 Defaults: /var/cache/davfs2 and ~/.davfs2/cache
401 cache_size
404 The amount of disk space in MiByte that may be used. mount.davfs
405 will always take enough space to cache open files, ignoring this
406 value if necessary.
407 Default: 50
408 table_size
411 mount.davfs maintains a hash table with an entry for each known
412 file or directory. This gives the number of entries in this ta‐
413 ble. For large file systems (more than some hundreds of files)
414 increasing this number may speed up file operations. The value
415 should be a power of 2.
416 Default: 1024
417 dir_refresh
420 After mount.davfs has got information about files in a directory
421 it considers it valid for this time in seconds. Note: This does
422 not affect opening of files and reading a directory by an appli‐
423 cation.
424 Default: 60
425 file_refresh
428 When a file or directory is opened by an application,
429 mount.davfs will first check the server for a newer version. But
430 some applications do open calls on the same file in short
431 sequence. To avoid unnecessary traffic mount.davfs will wait
432 that many seconds before it send a new request for the same
433 information.
434 Default: 1
435 delay_upload
438 When a file that has been changed is closed, mount.davfs will
439 wait that many seconds before it will upload it to the server.
440 This will avoid uploading of temporary files that will be
441 removed immediately after closing. If you need the files to
442 appear on the server immediately after closing, set this option
443 to 0.
444 Default: 10
445 gui_optimize
448 When a file is opened, mount.davfs will have to check the server
449 whether there is a newer version. Graphical User Interfaces tend
450 to open just any file, slowing down things dramatically for
451 large directories. With this option mount.davfs will try to get
452 this information from all files in a directory with one PROPFIND
453 request. 0 = no, 1 = yes.
454 Default: 0
455 minimize_mem
458 davfs2 holds information about files and directories in the
459 working memory. It will stay there as long as the file system is
460 mounted and the file is not deleted. By this memory usage by
461 davfs2 will grow over time and may slow down davfs2. With this
462 option set to 1 davfs2 will regularly clean the memory from
463 information that has not be used for some time. 0 = no, 1 =
464 yes.
465 Warning: Most file attributes are only maintained locally
466 because there is no corresponding WebDAV property. So if users
467 change attributes (owner, group, access bits) locally this
468 changes will be lost and attribute values will be reset to the
469 default values.
470 Default: 0
471
475 debug Send debug messages to the syslog daemon. The value tells what
476 kind of information shall be logged. The messages are send with
477 facility LOG_DAEMON and priority LOG_DEBUG. It depends from the
478 configuration of the syslog daemon where the messages will go
479 (propably /var/log/messages, /var/log/syslog or /var/log/dae‐
480 mon.log). Whether HTTP related debug messages are available
481 depends on your neon library.
482 Unlike other options, this option is cumulative. If there are
483 several debug entries with different values, all of them will be
484 applied. Also debug options from /etc/davfs2/davfs2.conf and
485 ~/.davfs2/davfs2.conf are merged.
486 Note: Debug messages let the log-files grow quickly. Never use
487 this option in normal operation of mount.davfs.
488 Default: no debugging messages
489 Recognized values:
491 config Command line and configuration options.
493 kernel Upcalls from the kernel file system.
495 cache Cache operations like adding and removing nodes.
497 http HTTP headers.
499 xml Parsing of the XML-body of WebDAV-requests.
501 httpauth
503 Negotiation of authentication.
504 locks Information about locks.
506 ssl TLS/SSL related stuff like certificates.
508 httpbody
510 Complete body of HTTP-responses.
511 secrets
513 Also print confidential information, which is usually
514 omitted or obscured.
515 most Includes config, kernel, cache and http.
517
521 This man page was written by by Werner Baumann <werner.baumann@online‐
522 home.de>.
523
527 http://savannah.nongnu.org/projects/davfs2
528
532 mount.davfs(8), umount.davfs(8), mount(8), umount(8), fstab(5)
533davfs2 2014-06-09 davfs2.conf(5)