You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the webserver should return a response has the 'application/davmount+xml' mime-type and can be saved as an xml file with a .davmount file extension.
Alternatively, some webdav tools install a protocol handler for the 'dav:' uri scheme which seems blessed by the IETF, but it seems that is considered bad form by some folk.
The issue with dav:// URL schemes is that not all browsers will pass these to the registered application for the scheme. It works in Safari here but not in Chrome.
This sounds really interesting. Is it planned to implement this?
Maybe then cyberduck would be the right tool for our customers to use together with our own product.
RFC4709 is the recommended way to get browsers to open an external webdav tool.
It looks like the webserver should return a response has the 'application/davmount+xml' mime-type and can be saved as an xml file with a .davmount file extension.
Alternatively, some webdav tools install a protocol handler for the 'dav:' uri scheme which seems blessed by the IETF, but it seems that is considered bad form by some folk.
The text was updated successfully, but these errors were encountered: