Webdav -> what url to map to?

[sebastienbo]

Hi guys,

I'm setting up webdav but I run into a problem:

When you enable webdav on qts 4.1 and later you get two choices (webdav permission or file share permission)
When I choose the old way to do it "Webdav permissions" I get in the file station the wel known webdav access permissions dropdown where I can configure the shares on which to grant wedav access.
But the newer option "Fileshare permissions" removes the webdav access dropdown option, and it is also nowhere documented on how to setup shares for this method...(it always references to the webdav permission part)

Can anyone help me?
What is the webdav url that i need to use? http://www.myserver.com/Sharename ?

[schumaku]

But the newer option "Fileshare permissions" removes the webdav access dropdown option, and it is also nowhere documented on how to setup shares for this method...

... WebDAV follows the Share Folder access rights as set-up for Windows File Server access, for AFP, for FTP(ES), ... hm, can you iterate why this is unclear?

What is the webdav url that i need to use? http://www.myserver.com/Sharename ?

Almost .. .ideally make use of https ... https://[NAS]:8081/[Sharefolderame]/ i.e. https://www.myserver.com:8081/Sharename/

Works like a charm on OS X Finder, on Windows whit ie. NetDrive2, ...

[pwilson]

It also works from Linux without challenge here.

[emersonvier]

This address http://xxxxx.myqnapcloud.com/t123 work by NETDRIVE on WIN 7.

But I try the same address on WIN 8.1 does not work with out NETDRIVE.

Can I use WEBDAV on WIN 8.1?

[sebastienbo]

Yes, but you need to purchase an ssl certificate for the hostname that you are trying to access.
I for example have a custom domain name (example.com) that has cname record to a dyndns hostname .
In that case I had to buy an alpha ssl certificate for example.com and install it on the nas.
But I know that you can buy a qnap cloud certificate, so that it is less complicated to install.

The certificate is ncessary because windows doesn't allow unsecure connections.

[schumaku]

This address http://xxxxx.myqnapcloud.com/t123 work by NETDRIVE on WIN 7. But I try the same address on WIN 8.1 does not work with out NETDRIVE.

Worked nicely on Windows 8.1 as well as now on Windows 10 using current NetDrive2 ()2.5.8 build 206 as of writing using the depreciated http://xxxxx.myqnapcloud.com/t123 as well as https://xxxxx.myqnapcloud.com:8081/t123 - with the QNAP NAS default certificate, as well as with certificates not commonly trusted by Windows, ie. by cacert.org (with both matching and non-matching URLs).

If you intend to use the very limited WebDAV coming with Windows ... well, the start is what @sebastioenbo is talking about.

Regards,
-Kurt.

[sebastienbo]

limited webdav functionanlity?

Schumaku, could you explain in what sense the webdav features of native windows will be limited compared to using netdrive?

ps: I use the native windows feature, because that doesn' t make me depen-dant from thrirdpart software, it would even allow me to connect to my webdav from every machine in the world even if i'm not adminsitrator (you must be admin to install software).
Ps 2 : I was not aware that build-in webdav feature would be more limited then the webdav implementation of windows, so I'm curious knowing what kind of "very limited" functionality I'm faced too

[schumaku]

It's great you are happy with it - the Windows one works for me ... under most conditions (sometimes we see requests to provide a client auth certificate, despite of there is no such request by the Web server...) - for many NAS users, it's a pain for several reasons.

[solarflysam]

I might be being stupid but I can't seem to find the answer or I am doing something wrong
Netdrive3 installed
WebDAV turned on QNAP with dedicated WebDAV ports enabled for https 5001

What url am I meant to use on netdrive3 though, my Qnap smart url doesn't work "https://qlink.to/****" and neither does https://********.myqnapcloud.com:5001