Description of problem (from the upstream bug):
[reply] [−] Description Debarshi Ray [reporter] [gnome-online-accounts developer] 2017-06-07 13:59:14 CEST

When adding a Nextcloud account, unless one explicitly specifies the URI scheme, it assumes that it is HTTPS. However, if someone specifies HTTP, it will stick to it.

This leads to a strange problem with my.owndrive.com. Sending a GET request to http://my.owndrive.com/remote.php/webdav evokes a successful (200) response, which is fine. However, an OPTIONS request leads to a 301 redirect with the Location header set to https://my.owndrive.com/remote.php/webdav. ie. the HTTPS equivalent of the same URL.

Therefore, if one explicitly specifies HTTP in Settings -> Online Accounts, the account will be added because it uses GET requests. However, GVfs' WebDAV backend won't be able to mount it because it sends an OPTIONS request and the redirect handler refuses to grant the redirect request.

A quick reading of the WebDAV backend code makes me think that redirects are tied to G_FILE_QUERY_INFO_NOFOLLOW_SYMLINKS. So, while we might be able to make the backend deal with this, it might be easier to teach g-o-a to detect this when adding the account and only advertise the HTTPS URL.

Version-Release number of selected component (if applicable):
libsoup-2.56.0-2.el7.x86_64
gvfs-1.30.4-3.el7.x86_64
gnome-online-accounts-3.22.5-1.el7.x86_64
gvfs-goa-1.30.4-3.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create ownCloud account in GOA on http://my.owndrive.com
2. Start Nautilus and go to the ownCloud shortcut created there
3.

Actual results:
Error message:
Unable to access 'desktopqe.com' HTTP Error: Moved Permanently

Expected results:
redirect should happen silently behind the scenes, if it needs to happen

Additional info: