Red Hat Bugzilla – Bug 503112
gnome-vfs2 webdav dislikes commas in directory path
Last modified: 2015-03-03 17:40:29 EST
Description of problem:
Using nautilus to mount a webdav share should work even when there is a comma in the directory path, but instead all access beneath the point of the comma is Empty and a refresh of the directory including the comma says the directory does not exist.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mount a webav share
2. create a folder with a comma in its name
3. try to use the folder
Says directory is empty or does not exist
OS X and Ms Windows both can access and use the directory, gnome should to.
Can you post example of the URI?
Can you try escaping the comma in the URI with something like %2C ?
Does it happen when just browsing the structure - i.e. does Nautilus produce bad URI itself?
Browsing? nautilus mounts the share in a drive like fashion. With the comma in the path you get an empty directory at a_comma and never see the file in.it at all.
From cursory testing (logs, some sniffing) it looks like nautilus is sending the correct URI with the %2C in it, it looks like nautilus is choking on the server response. I use Apache with mod_davfs, but that should not matter as both OS X and MS Windows do not exhibit the issue using the same server.
You can even use nautilus to add the comma, and as best as I can tell you can still add things to the directory using nautilus, just not see them, and nautilus tells you that a_comma does not exist if you refresh its contents.
Confirming, reproduced locally.
Looks like an URI encoding issue, gnomevfs-ls can list the contents in simple form (davs://test.server.com/this,path/has/a_comma/) fine, fails with %2C (which is done by Nautilus automatically).
Fedora 10 and later is fine. Waiting for proper acks.
Particular gnome-vfs2 commit fixing the issue: http://git.gnome.org/cgit/gnome-vfs/commit/?id=c1dc878e453edeff6cb63f655d2a8d70cf7f6418
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.