Created attachment 857983 [details] output of "GVFS_HTTP_DEBUG=all /usr/libexec/gvfsd -r" during test Description of problem: nautilus and gvfs-mount is mounting correctly the webdav folder, but when trying to access a password protected zone, it says "Authorization Required" without asking username and password The same webdav folder is working fine with cadaver. Version-Release number of selected component (if applicable): gvfs-1.18.3-2.fc20.x86_64 How reproducible: Steps to Reproduce: $ gvfs-mount davs://LoginName.fr/LoginName $ gvfs-mount -i -l ... Mount(0): LoginName sur system.domain.fr -> davs://LoginName.fr/LoginName Type: GDaemonMount default_location=davs://LoginName.fr//LoginName themed icons: [folder-remote] [folder] symbolic themed icons: [folder-remote-symbolic] [folder-symbolic] [folder-remote] [folder] can_unmount=1 can_eject=0 is_shadowed=0 $ gvfs-ls davs://LoginName.fr//LoginName prive public www $ gvfs-ls davs://LoginName.fr/LoginName/www testdir $ LANG=C gvfs-copy index.html davs://LoginName.fr/LoginName/www/ Error copying file index.html: Erreur du client HTTP?: Authorization Required Actual results: Error 401 "Authorization Required" Expected results: Username and password prompt Additional info: GVFS_HTTP_DEBUG=all set before running gvfsd, all data gathered in attachment We see a "WWW-Authenticate: Basic" that ends with 401 Extract from the log: GVFS_HTTP_DEBUG=all /usr/libexec/gvfsd -r ... (process:4064): libsoup-CRITICAL **: soup_auth_authenticate: assertion 'password != NULL' failed < HTTP/1.1 401 Authorization Required < Soup-Debug-Timestamp: 1391204439 < Soup-Debug: SoupMessage 6 (0x7f6af4023c90) < Date: Fri, 31 Jan 2014 21:40:39 GMT < Server: Apache/2.2.9 (Debian) DAV/2 PHP/5.2.6-1+lenny16 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g < WWW-Authenticate: Basic realm="CartFab" < Vary: Accept-Encoding < Content-Encoding: gzip < Content-Length: 290 < Keep-Alive: timeout=15, max=100 < Connection: Keep-Alive < Content-Type: text/html; charset=iso-8859-1
Precision: this webdav server is working fine with cadaver, and is also being accessed fine by a lot of users using NetDrive, Konqueror/Dolphin... litmus compliance test is OK (see 2nd attachment). FYI, I let appear a dummy sytem name in the logs , but I can provide in private the real webdav server name.
Created attachment 858046 [details] litmus webdav compliance check
Hey! Unfortunately there isn't api to ask for credentials if a share is already mounted. However I think GVfs should ask for password if you try to mount the "private" path directly: gvfs-mount dav://server/path/to/private Does it work?
Yes. The problem in fact is that we have 3 subfolders per user (www/public/private) on server side with different permissions (the apache configuration is a little bit odd). Mounting straight a "really" private path is working fine, we get the correct authentication request at mount time, then we can full access the folder: $ gvfs-mount davs://LoginName.fr/LoginName/private Password: $ gvfs-copy file.txt davs://LoginName.fr/LoginName/private $ gvfs-ls davs://LoginName.fr/LoginName/prive file.txt $ gvfs-mount -u davs://LoginName.fr/LoginName/private Mounting the two other folders (either www or public) is possible anonymously, but we do not get then the authentication prompt when trying to write there: $ gvfs-mount davs://LoginName.fr/LoginName/public $ gvfs-ls davs://LoginName.fr/LoginName/public $ gvfs-copy file.txt davs://LoginName.fr/LoginName/public Error copying file file.txt: Erreur du client HTTP?: Authorization Required $ gvfs-mount -u davs://af18148h.fr/af18148h/public Other webdav clients are handling it correctly... Right, sounds close to "GNOME Desktop 590007" bug.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I believe this still is a problem with at least F24
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
as far as I can seem issue still remain on F26
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.