I think I've found a bug in davfs2. When I mount a DAV
volume containing collection names with nested escape
sequences --- for instance, the name 'foo bar%20baz'),
davfs2 decodes the escape sequences, producing the
(incorrect) name 'foo bar baz'.
cadaver and the Windows built-in dav client handle
these dirnames correctly (they show up as 'foo bar%20baz'.
If you look at the network trace, the dirname is
...the space between 'foo' and 'bar' is escaped to %20
and the '%20' between 'bar' and 'baz' is escaped to
'%2520'. Davfs2 should strip off just one layer of
escaping, yielding 'foo bar%20baz', but it strips off
both layers. I suspect that ne_path_escape might be
being called twice on the same pathname.
I'd be happy to supply any other info that might help.