1davfs2.conf(5)                       1.6.0                      davfs2.conf(5)
2
3
4

NAME

6       davfs2.conf - Configuration file for mount.davfs
7
8
9

DESCRIPTION

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
18
19       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
23
24       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
31
32

EXAMPLE

34       proxy     foo.bar:8080
35       use_locks 0
36       [/media/dav]
37       use_locks 1
38       [/home/otto/mywebspace]
39       gui_optimize 1
40
41
42       All  mounted davfs2 file systems will use the proxy foo.bar. All davfs2
43       file systems except /media/dav will  disable  the  use  of  the  locks.
44       /home/otto/mywebspace will use the gui_optimize option.
45
46

GENERAL SYNTAX RULES

48       Lines that only contain spaces and tabs (empty lines) are ignored.
49
50
51       # indicates a comment. The rest of the line is ignored.
52
53
54       \ is the escape character.
55
56
57       "" is used for quotation.
58
59
60       If  a value contains one of the special characters space, tab, #, \, or
61       ", this character must be escaped by a preceding \. Use ’\ ’ instead of
62       ’ ’, ’\#’ instead of ’#’, ’\\’ instead of ’\’ and ’\"’ instead of ’"’.
63
64
65       Values  containing  spaces, tabs or # may instead be enclosed in double
66       quotes.  But " and ’ must be escaped even within double quotes. If  the
67       starting  line  of  a  section is enclosed in double quotes, the square
68       brakets must be within the quotes (like "[/home/otto/with space]").
69
70
71       Boolean option values (yes/no) must be given as numerical value.  0 for
72       no, 1 for yes.
73
74
75

AVAILABLE CONFIGURATION OPTIONS

General Options

78       dav_user
79              When  invoked  by  root  the mount.davfs daemon will run as this
80              user.  Value must be given as name, not as numerical id.
81              Default: davfs2
82              Only allowed in the system wide configuration file.
83
84
85       dav_group
86              The group of the running mount.davfs daemon. Ordinary users must
87              be  member of this group in order to mount a davfs2 file system.
88              Value must be given as name, not as numerical id.
89              Default: davfs2
90              Only allowed in the system wide configuration file.
91
92
93       buf_size
94              Size in KiByte of the buffer used to communicate with the kernel
95              file system.  Only useful with fuse, where read and write opera‐
96              tions may profit from a larger buffer.
97              Default: 16
98
99
100
102       use_proxy
103              Whether to use a proxy to connect to the WebDAV server. 0 =  no,
104              1 = yes.  If no proxy is defined in the configration file or the
105              environment variables  https_proxy,  http_proxy  and  all_proxy,
106              this option has no effect.
107              Default: 1
108              Only allowed in the system wide configuration file.
109
110
111       proxy  Name  of  the proxy. The name must be the fully qualified domain
112              name (no scheme). If the proxy port differs from the default  of
113              8080,  it  must  be  appended,  separated  by a colon. Examples:
114              foo.bar:1704 or foo.bar
115              Only allowed in the system wide configuration file.
116
117
118       trust_ca_cert
119              Name of a certificate file in PEM format. The name of  the  file
120              may  be given as absolute path or as file name only. In the lat‐
121              ter case the directories ~/.davfs2/certs  and  /etc/davfs2/certs
122              will be searched.
123              This  option  is  useful  when  the certificate presented by the
124              server cannot be  verified  using  the  system's  data  base  of
125              trusted  certificate authorities (CA). The certificate file must
126              contain the self-signed certificate of the top level CA  in  the
127              chain  of trust. It may be a self-signed server certificate (but
128              see also trust_server_cert).  With this option the  system's  CA
129              data base is ignored.
130              Note:  Even if the server's certificate is trusted that does not
131              mean it is accepted. Additionally the certificate's date must be
132              valid and either the CommonName or the SubjectAltName must match
133              the host name of the server.
134
135
136       servercert
137              Same as trust_ca_cert but badly named.
138              Deprecated
139
140
141       trust_server_cert
142              Name of a certificate file in PEM format. The name of  the  file
143              may  be given as absolute path or as file name only. In the lat‐
144              ter case the directories ~/.davfs2/certs  and  /etc/davfs2/certs
145              will be searched.
146              Useful  when  the  server's  certificate can't be verified or is
147              even invalid, but you know that you can trust this  certificate.
148              When  the server presents a certificate that is exactly equal to
149              this one and when the server is able to authenticate against the
150              public  key contained in this certificate the connection will be
151              established.
152              This is the preferred option for  self  signed  server  certifi‐
153              cates.
154              No  other  ways  to verify the certificate will be tried and the
155              certificate will not be checked for validity.
156
157
158       clientcert
159              Name of a certificate in PKCS#12 format that  will  be  used  to
160              authenticate  with the server. The name of the file may be given
161              as absolute path or as file name only. In the  latter  case  the
162              directories  ~/.davfs2/certs/private  and /etc/davfs2/certs/pri‐
163              vate will be searched.
164              Warning: If the client certificate is issued by an  intermediary
165              CA and not by a top level CA then the TLS-specification requires
166              the client to send the complete chain of  certificates  (without
167              the top level CA-certificate). davfs2 only sends the client cer‐
168              tificate. To work around this bug  the  server  must  store  and
169              trust  the  complete chain of CA-certificates down to the one CA
170              that isssued the client certificate.
171
172
173       secrets
174              Name of a file that holds the credentials for  servers  and  the
175              proxy, and passwords to decrypt the client certificate. The name
176              must be an absolute path. The file must be read and writable  by
177              the owner only (mode 600).
178              Default: ~/.davfs2/secrets
179              Only  allowed  in  the  user configuration file. The system wide
180              secrets file is always /etc/davfs2/secrets.
181
182
183       ask_auth
184              Ask the user interactively for credentials and passwords if  not
185              found in the secretsfile. Ask the user if a servercert cannot be
186              verified. 0 = no, 1 = yes.
187              Default: 1
188
189
190       use_locks
191              Whether to lock files on the server when  they  are  opened  for
192              writing.  0 = no, 1 = yes.
193              Default: 1
194
195
196       lock_owner
197              A  string send to the server to identify the owner of a lock. If
198              a WebDAV resource is used at the same time by different  clients
199              using  the  same  credentials,  different  values for lock_owner
200              should be chosen.
201              Default: the username from the credentials
202
203
204       lock_timeout
205              How long in seconds locks should be  valid,  before  the  server
206              removes  them.  The server may ignore this and set its own time‐
207              out value.
208              Default: 1800
209
210
211       lock_refresh
212              That many seconds before the lock times  out,  mount.davfs  will
213              try  to  refresh  the  lock.  The  value should be substantially
214              greater than delay_upload.
215              Default: 60
216
217
218       use_expect100
219              To avoid  uploading big  files  that  will  be  refused  by  the
220              server,  mount.davfs uses the header expect: 100-continue to get
221              the o.k.  from the server  before  uploading.  Not  all  servers
222              understand this.  0 = no, 1 = yes.
223              Default: 0
224
225
226       if_match_bug
227              Some  servers  do  not handle If-Match and If-None-Match-headers
228              correctly.  This otion tells mount.davfs to use HEAD instead  of
229              thes headers.  0 = no, 1 = yes.
230              Default: 0
231
232
233       drop_weak_etags
234              Popular  servers  send a weak etag whenever they are not able to
235              calculate a strong one. This weak etag will never be valid,  but
236              after  one  second  it  is  silently turned into a strong, valid
237              etag. With this flag set to 1, mount.davfs will never  use  this
238              weak  etags.  If  the  flag is 0, the weakness indicator will be
239              removed and the etag is assumed to be strong. There is some dan‐
240              ger  of  the  Lost-Update-Problem with this. But it is minimized
241              when using locks.
242              You should turn this on, when you can't use locks and  there  is
243              the  danger  of  concurrent access to the same resource. In this
244              case the etag is not used at all  and  the  resource  cannot  be
245              cached.
246              0 = no, 1 = yes.
247              Default: 0
248
249
250       n_cookies
251              Some  servers  will  only  work  when  they are allowed to set a
252              cookie and this cookie is returned in subsequent requests.  This
253              option  sets the number of cookies you are willing to accept and
254              include in subsequent requests. davfs2 will only  care  for  the
255              name  and the value of the cookie and ignore all of the possible
256              attributes.
257              Default: 0
258
259
260       precheck
261              If option if_match_bug is set: use HEAD-requests  to  check  for
262              existence  or  modification  of a file to avoid unintended over‐
263              writing what somebody else changed.  Has  no  effect  if  option
264              if_match_bug is 0. You should only set it 0, if there is no con‐
265              current access to the server.  0 = no, 1 = yes.
266              Default: 1
267
268
269       ignore_dav_header
270              Some servers send wrong information about their capabilities  in
271              the DAV-header.  In this case the header should be ignored.
272              Default: 0
273
274
275       use_compression
276              Use  gzip-compression for downloading files, if supported by the
277              server.  Uploads will still be uncompressed.
278              Default: 0
279
280
281       min_propset
282              Some servers are reported to significantly slow  down  when  the
283              Etag  and  Last-Modified  properties  are requested. This option
284              will reduce the set  of  WebDAV-properties  requested  from  the
285              server  to  the minimal set. Don't use it if your file system is
286              used for reading and  writing.  Without  Etag  or  Last-Modified
287              davfs2 will not be able to check for changes on the server which
288              may result in  unnecessary  downloads  and  lost  updates.  This
289              option  will  also  effectively disable caching of files because
290              files in the cache can't be reused.
291              Default: 0
292
293
294       follow_redirect
295              If the server redirects a GET-request to  a  different  resource
296              (maybe on a different server) then follow this redirection.
297              Currently there are some restrictions: all redirects are treated
298              as temporary redirects; if the new server  requires  authentica‐
299              tion  then  the  same  credentials  are  use as for the original
300              server; if the connection is over  TLS  the  server  certificate
301              will  be  checked  against  the trusted CAs known by the system;
302              user configured server certificates and client certificates  are
303              not used for the new server.
304              Default: 0
305
306
307       sharepoint_href_bug
308              SharePoint  does  not properly encode UTF8-characters within the
309              href-element.  Because of this some files are invisible  because
310              the  href-element  violates the rules. Neon 0.31 and newer has a
311              workaround for this SharePoint bug. This  option  will  activate
312              this workaround.
313              Default: 0
314
315
316       server_charset
317              When  extracting  file names from the path component of the URL,
318              mount.davfs will assume they are encoded  using  this  character
319              set and translate file names to the local character set. This is
320              not about encoding of file contents and not about HTTP  escaping
321              rules.
322              There  is no means in HTTP to know the character encoding of the
323              path component. There may be even different encodings within the
324              same path, as the encoding of file names is often defined by the
325              clients that created them.  Nowadays it  is  best  to  use  only
326              UTF-8 encoding and to do no conversion. If you are not sure that
327              all clients  understand  UTF-8,  restrict  file  names  to  pure
328              us-ascii.  Never  use  characters in file names, that may have a
329              special function on some operating systems (like /, : and \).
330              Default: no character set conversion
331
332
333       connect_timeout
334              When creating a TCP connection to the  server  mount.davfs  will
335              wait  that  many seconds for an answer before assuming an error.
336              If a value of '0' is used then no explicit timeout  handling  is
337              set  and  the  connect call will only timeout as dictated by the
338              TCP stack.
339              This parameter only takes effect if the version of neon  in  use
340              (neon version > 0.26) and the OS support non-blocking I/O.
341              Default: 10
342
343
344       read_timeout
345              How long in seconds mount.davfs will wait for an answer from the
346              server before assuming an error.
347              Default: 30
348
349
350       retry  When mount.davfs can not reach the  server  it  will  try  again
351              after retry seconds. For subsequent retries the interval will be
352              increased up to max_retry seconds.
353              Default: 30
354
355
356       max_retry
357              Maximum value of the retry interval.
358              Default: 300
359
360
361       max_upload_attempts
362              When uploading a changed file fails temporarily mount.davfs will
363              retry with increasing intervals, but not more often than this.
364              With  a  bad  connection  this will cause additional traffic. To
365              reduce  traffic   caused   by   unsuccessful   attempts   option
366              use_expect100  can  be set. But please test it. Most proxies and
367              some servers don't support this header.
368              Default: 15
369
370
371       add_header
372              Your server might expect special headers to do  what  you  want.
373              Different  from  other  options,  this one takes two values: the
374              name of the header and its value.  Some ASP-backends to IIS seem
375              to require the Microsoft specific header "Translate: F". You can
376              add it like this:
377              add_header Translate F
378              mount.davfs will add header "Translate: F" on all requests.
379              This  option  is  cumulative.  You  can  enter  more  than   one
380              add_header option and all of them will be added. Also add_header
381              options from /etc/davfs2/davfs2.conf  and  ~/.davfs2/davfs2.conf
382              are merged.
383
384
385
387       backup_dir
388              Each mounted davfs2 file system has a directory to store backups
389              of files that could not be stored back to the server. This  sets
390              the  name  of  this  directory.  You should regularly check this
391              directory.
392              Default: lost+found
393
394
395       cache_dir
396              The directory where mount.davfs will  store  cached  files.  For
397              every mount point a subdirectory will be created.
398              In  the  systemwide  configuration file this will set the system
399              wide cache, used by root. In a users configuration file it  will
400              set the cache used by this user.
401              Defaults: /var/cache/davfs2 and ~/.davfs2/cache
402
403
404       cache_size
405              The amount of disk space in MiByte that may be used. mount.davfs
406              will always take enough space to cache open files, ignoring this
407              value if necessary.
408              Default: 50
409
410
411       table_size
412              mount.davfs  maintains a hash table with an entry for each known
413              file or directory. This gives the number of entries in this  ta‐
414              ble.  For  large file systems (more than some hundreds of files)
415              increasing this number may speed up file operations.  The  value
416              should be a power of 2.
417              Default: 1024
418
419
420       dir_refresh
421              After mount.davfs has got information about files in a directory
422              it considers it valid for this time in seconds. Note: This  does
423              not affect opening of files and reading a directory by an appli‐
424              cation.
425              Default: 60
426
427
428       file_refresh
429              When  a  file  or  directory  is  opened  by   an   application,
430              mount.davfs will first check the server for a newer version. But
431              some applications do open  calls  on  the  same  file  in  short
432              sequence.  To  avoid  unnecessary  traffic mount.davfs will wait
433              that many seconds before it send a  new  request  for  the  same
434              information.
435              Default: 1
436
437
438       delay_upload
439              When  a  file  that has been changed is closed, mount.davfs will
440              wait that many seconds before it will upload it to  the  server.
441              This  will  avoid  uploading  of  temporary  files  that will be
442              removed immediately after closing.  If you  need  the  files  to
443              appear  on the server immediately after closing, set this option
444              to 0.
445              Default: 10
446
447
448       gui_optimize
449              When a file is opened, mount.davfs will have to check the server
450              whether there is a newer version. Graphical User Interfaces tend
451              to open just any file,  slowing  down  things  dramatically  for
452              large directories.  With this option mount.davfs will try to get
453              this information from all files in a directory with one PROPFIND
454              request. 0 = no, 1 = yes.
455              Default: 0
456
457
458       minimize_mem
459              davfs2  holds  information  about  files  and directories in the
460              working memory. It will stay there as long as the file system is
461              mounted  and  the  file  is not deleted. By this memory usage by
462              davfs2 will grow over time and may slow down davfs2.  With  this
463              option  set  to  1  davfs2  will regularly clean the memory from
464              information that has not be used for some time.  0  =  no,  1  =
465              yes.
466              Warning:  Most  file  attributes  are  only  maintained  locally
467              because there is no corresponding WebDAV property. So  if  users
468              change  attributes  (owner,  group,  access  bits)  locally this
469              changes will be lost and attribute values will be reset  to  the
470              default values.
471              Default: 0
472
473
474

Debugging Options

476       debug  Send  debug  messages to the syslog daemon. The value tells what
477              kind of information shall be logged. The messages are send  with
478              facility  LOG_DAEMON and priority LOG_DEBUG. It depends from the
479              configuration of the syslog daemon where the  messages  will  go
480              (propably  /var/log/messages,  /var/log/syslog  or /var/log/dae‐
481              mon.log). Whether HTTP  related  debug  messages  are  available
482              depends on your neon library.
483              Unlike  other  options,  this option is cumulative. If there are
484              several debug entries with different values, all of them will be
485              applied.  Also  debug  options  from /etc/davfs2/davfs2.conf and
486              ~/.davfs2/davfs2.conf are merged.
487              Note: Debug messages let the log-files grow quickly.  Never  use
488              this option in normal operation of mount.davfs.
489              Default: no debugging messages
490
491              Recognized values:
492
493              config Command line and configuration options.
494
495              kernel Upcalls from the kernel file system.
496
497              cache  Cache operations like adding and removing nodes.
498
499              http   HTTP headers.
500
501              xml    Parsing of the XML-body of WebDAV-requests.
502
503              httpauth
504                     Negotiation of authentication.
505
506              locks  Information about locks.
507
508              ssl    TLS/SSL related stuff like certificates.
509
510              httpbody
511                     Complete body of HTTP-responses.
512
513              secrets
514                     Also  print  confidential  information,  which is usually
515                     omitted or obscured.
516
517              most   Includes config, kernel, cache and http.
518
519
520

AUTHORS

522       This man page was written by by Werner Baumann  <werner.baumann@online‐
523       home.de>.
524
525
526

DAVFS2 HOME

528       http://savannah.nongnu.org/projects/davfs2
529
530
531

SEE ALSO

533       mount.davfs(8), umount.davfs(8), mount(8), umount(8), fstab(5)
534
535
536
537davfs2                            2020-08-06                    davfs2.conf(5)
Impressum