GNOME file selector tries to access wrong path on WebDAV

Bug #18036 reported by Jürgen Kreileder
10
Affects Status Importance Assigned to Milestone
libgnomeui
Expired
Medium
libgnomeui (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

If there's a WebDAV server configured with something like
davs://<email address hidden>:441/users/name (unlike on Debian, the non-standard
port works on Ubuntu :-), the GNOME file selector shows that server in its
shortcut list on the left side. Clicking the entry results in an access to
".../users/". If the user only has access to ".../users/name" but not
".../users" then this fails with 401. That makes the entry in the file selector
pretty useless.

http://bugzilla.gnome.org/show_bug.cgi?id=150585: http://bugzilla.gnome.org/show_bug.cgi?id=150585

Revision history for this message
Sebastien Bacher (seb128) wrote :

is that specific to webdav? do you create the share with the nautilus dialog for it?

Revision history for this message
Jürgen Kreileder (jk) wrote :

No, it happens for FTP too: With ftp.kernel.org/pub/linux/kernel, it reads
everything up to / (that is /pub/linux/kernel, /pub/linux, /pub, and /) .

I guess the file selector does that when it builds the path buttons. It's not
clear to me why it has to access the all parent directories in the path for
that, it should be OK if just builds the buttons from the given string.

One can probably reproduce the problem locally with a shortcut for something
like /foo/bar/, where the user can access the directory /foo/bar but not the
parent /foo. I haven't tried that, though.

Revision history for this message
Jürgen Kreileder (jk) wrote :

The problem also shows up with directory combobox at the lower left of Nautilus
windows.

I think if a user mounts dav[s]://example.org/some/directory, then
'/some/directory' should be treated as file system root and GNOME shouldn't try
to access parent directories. (This behavior would be consistent with NFS)

Revision history for this message
Sebastien Bacher (seb128) wrote :

you describe 2 differents issues here. Your fileselector tries to open /users
where you have set /users/name? What does nautilus?

Revision history for this message
Jürgen Kreileder (jk) wrote :

Nautilus windows have a combobox that allows you to access parent directories in
the lower left corner: If you mount dav://host/parent/child, you'll get a
combobox with 'dav://host/' and 'dav://host/parent/' in the window for
'dav://host/parent/child'. That's just as wrong as giving access to those
directories in the file chooser.

GNOME should treat mount points (at least WebDAV and FTP) as file system roots:
 That means if a user mounts something like 'host/level1/level2/level3', he can
access everything below '.../level3' but nothing above that level. Windows gets
that right: going up from '.../level3' puts into the special 'Webfolders' folder.

Note that the tree view in Nautilus' browser mode shows the correct behavior, it
just presents stuff below '.../level3'.

Revision history for this message
Sebastien Bacher (seb128) wrote :

thanks, that part is clear. But "441/users/name .... Clicking the entry results
in an access to ".../users/" seems an another issue, it should use the right
directory, or is that a typo?

Revision history for this message
Jürgen Kreileder (jk) wrote :

(The '441' is just the port on the server).

* Mounted volume is dav://host:port/users/name/
* Open file selector
* Click on the corresponding entry in the shortcut list on the left

=> Accesses to dav://host:port/users/ and dav://host:port/
Both of these shouldn't occur.

Revision history for this message
Sebastien Bacher (seb128) wrote :

That seems to be the same issue than
http://bugzilla.gnome.org/show_bug.cgi?id=150585

Changed in libgnomeui:
status: Unconfirmed → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

confirmed by upstream

Changed in libgnomeui:
status: Unconfirmed → Confirmed
Changed in libgnomeui:
assignee: seb128 → desktop-bugs
Changed in libgnomeui:
status: Confirmed → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue on hardy?

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing this bug since now the gtk gio backend is used in intrepid

Changed in libgnomeui:
status: Triaged → Invalid
Changed in libgnomeui:
importance: Unknown → Medium
Changed in libgnomeui:
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.