gvfs refuses to authenticate to webdav share after mounting

Bug #260988 reported by Stefanr
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gvfs
Expired
High
gvfs (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

Using Ubuntu Hardy, we cannot delete or create files or folders on our webdav share anymore. Connecting to a Gallery2 webdav share (nautilus dav://hostname/g2/w/) which allows anonymous reading works. When trying to upload a photo, we expect an authorization dialog, but nautilus only says "Authorization required", letting me skip or cancel. This works as expected in Feisty and in some other operating system.

When we disable anonymous access to Gallery2, we can authenticate through Nautilus at mount time and uploading works fine.

Tcpflow of a failed session shows the obvious: first a PROPFIND on the directory, server replies 207, then a HEAD on the file gets a 401, then the file gets put and the server replies again with a 401.

When I try to read the gvfs source code, I see in daemon/gvfsbackenddav.c that at mount time authentication is governed by a function called "soup_authenticate_interactive". After a successful mount, the authentication handler gets switched to soup_authenticate_from_data. That sounds a little suspicious to me. I am hardly a programmer, so I have not yet gotten it to work when I play with the handlers, but maybe someone else can.

I would have made this a duplicate of #206439, but the code between the various backends seems a little too separate for that.

We have gvfs version 0.2.5-0ubuntu2 installed.

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

thank you for your bug report, that is an upstream issue, could you open the bug on bugzilla.gnome.org where the people writting the code can reply?

Changed in gvfs:
assignee: nobody → desktop-bugs
importance: Undecided → Low
Revision history for this message
Stefanr (stefan-stefanlinux) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for sending the bug to GNOME

Changed in gvfs:
status: New → Triaged
Changed in gvfs:
status: Unknown → New
Changed in gvfs:
importance: Unknown → High
Changed in gvfs:
status: New → 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.