After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 572429 - Nautilus can't mount a webfolder if the URI path contains an ampersand character
Nautilus can't mount a webfolder if the URI path contains an ampersand character
Status: RESOLVED DUPLICATE of bug 561515
Product: gvfs
Classification: Core
Component: webdav backend
unspecified
Other All
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-02-19 15:32 UTC by Werner Randelshofer
Modified: 2011-05-14 10:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Werner Randelshofer 2009-02-19 15:32:37 UTC 
Please describe the problem:
When I try to mount a webfolder using an URI which contains an ampersand (&) character in the path, Nautilus displays an error message.

For example, an URI like this one can not be mounted:

davs://server.com/technocology%20&%20architecture



Steps to reproduce:
1. Start Nautilus.
2. Mount a webfolder URI which contains an ampersand, for example davs://server.com/technocology%20&%20architecture



Actual results:
Nautilus displays the following error message:

"Could not display
"davs://server.com/technocology%20&%20architecture".
  Error: Response invalid
  Please select another viewer and try again."


Expected results:
Nautilus should mount the webfolder, because an URI path may contain ampersand characters according to RFC 3986.

Does this happen every time?
Yes.

Other information:
Comment 1 Alexander Larsson 2009-03-05 12:25:21 UTC 
Does it work if you escape the & as %26?
Comment 2 Werner Randelshofer 2009-03-05 13:20:09 UTC 
No, this does not help.

I noticed that when I type %26 in the URL, in the message dialog this is expanded to %2526. I don't know whether this is just a problem of the message dialog though.
Comment 3 awilliam 2010-03-23 19:29:10 UTC 
Possibly Bug#561515, Bug#572429, and Bug#455585 are all related or duplicates?
Comment 4 Werner Randelshofer 2010-03-23 20:15:23 UTC 
Yes, they all seem to be related. You can combine them into a single problem report.

I think the problem can be generalized into the following description:

Handling of WebDAV file names is broken in Nautilus, if the filename contains URI special characters as described in rfc2396, chapter 2.2 "Reserved Characters".

Best,
Werner
Comment 5 Werner Randelshofer 2010-03-23 20:30:21 UTC 
Um, I shouldn't have posted so soon.

I think we should note, that the special characters which occur in the filename are properly encoded in the URI (or URL for that matter).

Also rfc2396 is obsolete. I should have quoted rfc3986.

Okay, here it comes again:


Handling of WebDAV file names is broken in Nautilus, if the filename contains
reserved characters as described in rfc3986, chapter 2.2 "Reserved
Characters". 

The WebDAV server in question (ILIAS Learning Management System) does properly use escape encoding for reserved characters as described in chapter 2.2 in rfc3986.


hth,
Werner
Comment 6 Christian Kellner 2011-05-09 22:02:05 UTC 
Very likely a dup of bug 561515. In the case of the example url it would joke already on the spaces that are in the url (and also on the ampersand).
Comment 7 Christian Kellner 2011-05-14 10:05:03 UTC 
I made some local tests with fixes that I came up with for bug 561515 and with those fixes applied the ampersand character works fine. I am pretty much convinced now that this is a dup of 561515.

*** This bug has been marked as a duplicate of bug 561515 ***