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 604070 - Nautilus doesn't prompt for WebDAV password if it is needed for writing only
Nautilus doesn't prompt for WebDAV password if it is needed for writing only
Status: RESOLVED DUPLICATE of bug 549415
Product: gvfs
Classification: Core
Component: webdav backend
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-12-08 13:24 UTC by Eric Martel
Modified: 2011-05-07 16:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Eric Martel 2009-12-08 13:24:27 UTC
If in Apache I set a Dav directory with the following limit (read is allowed for everyone, but only authenticated users can write to it):

<Limit POST PUT DELETE>
     Require valid-user
</Limit>

Using a dav:// URL, Nautilus will access this directory in read mode, which is OK. However, if I try to put something into the directory, Nautilus won't prompt me for a password and just give me an access denied error.

If I try the same thing using Konqueror (with a webdav:// URL), Konqueror will also give me normal access in read mode, but if I try to put something into the directory then it will prompt me for a password and the transfer will then successfully occur: that is the expected behavior.
Comment 1 Eric Martel 2009-12-08 13:30:11 UTC
I simply want to specify that the password prompting works correctly when read access is also limited to authenticated users.
Comment 2 Cosimo Cecchi 2011-04-12 15:50:59 UTC
-> gvfs

I think this is a bug in the dav backend.
Comment 3 Tomas Bzatek 2011-04-13 10:56:31 UTC
This is known, planned Remount Operation feature will handle this.
Comment 4 Christian Kellner 2011-05-07 16:31:31 UTC
Actually a duplicate of bug 549415.

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