New issue
Advanced search Search tips

Issue 818470 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Add support for RFC4709: Mounting Web Distributed Authoring and Versioning (WebDAV) Servers

Reported by minf...@sharp.fm, Mar 3 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/604.5.6 (KHTML, like Gecko) Version/11.0.3 Safari/604.5.6

Steps to reproduce the problem:
Add support for RFC4709: Mounting Web Distributed Authoring and Versioning (WebDAV) Servers.

Right now, getting people to mount a webdav folder involves and end user following various complicated instructions to manually mount the server.

What should be possible is for the end user to click on a link, and have the process kicked off as if they clicked on Go -> Connect to Server (on a Mac) or "Add Network Location" (on Windows) and entered a webdav endpoint.

This will drastically reduce the administrative burden of configuring webdav drives, in an RFC compliant manner.

What is the expected behavior?

What went wrong?
RFC4709 not yet supported.

Did this work before? No 

Chrome version: 64.0.3282.186 (Official Build) (64-bit)  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
Labels: Needs-Triage-M64
Components: Platform>DevTools>Authoring
Labels: Triaged-ET M-67 FoundIn-67
Status: Untriaged (was: Unconfirmed)
The issue seems to be a feature request. Hence, marking it as untriaged for further inputs from dev team.

Thanks...!!

Comment 4 by caseq@chromium.org, Mar 5 2018

Components: -Platform>DevTools>Authoring

Comment 5 by tapted@chromium.org, Mar 12 2018

Components: Internals>Network Blink>Network
Labels: -OS-Mac
[mac triage] this doesn't seem OS specific. But also my initial thought is that I don't know if this belongs in a web browser. adding some network folks who might know.

Comment 6 by ricea@chromium.org, Mar 12 2018

Components: -Blink>Network -Internals>Network UI>Browser>Downloads
Labels: -Pri-2 Pri-3
Looking at RFC4709, it appears to rely on executing a file with a "application/davmount+xml" mimetype. So it mostly depends on whether there is software installed which handles that mimetype. This has very little to do with Chrome.

Sending to the Downloads component to see if there is a way to bypass the requirement to explicitly execute the file.

Comment 7 by minf...@sharp.fm, Mar 12 2018

It doesn't rely on executing any file, no.

The file contains XML metadata containing details of the server to connect to, such as it's name, port, and recommended username.

Comment 8 by minf...@sharp.fm, Mar 12 2018

On MacOS, the command to run in response to "application/davmount+xml" is mount_webdav, as follows:

https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man8/mount_webdav.8.html

Need to do some digging on the Windows and Linux variant equivalents.

Comment 9 by minf...@sharp.fm, Mar 12 2018

On Windows, it looks like the command to use to map the drive is https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/new-psdrive?view=powershell-6 - it is apparently also possible to leave off the drive letter to just make the path available.

Comment 10 by minf...@sharp.fm, Mar 12 2018

Appears the Linux command would be based on davfs2 at http://savannah.nongnu.org/projects/davfs2
Cc: qin...@chromium.org
Owner: dtrainor@chromium.org
Status: Assigned (was: Untriaged)

Comment 12 by ricea@chromium.org, Mar 30 2018

It's the responsibility of the software to register itself for the application/davmount+xml mimetype. That way it will work in all browsers.

I installed davfs2 on my machine. If it wanted to support RFC4709, it would need to place a file in /usr/lib/mime/packages/ to configure itself as the handler for  application/davmount+xml. But it doesn't.

Users can also configure it for themselves by creating a .mailcap file in their home directory.

Sign in to add a comment