Webdav with Jetbrains Rider, Caddy and ASP NET Core Umbraco CMS about caddy-webdav HOT 7 OPEN

Yeap that looks like webdav-ish. I think you can do webdav request with curl by doing something like curl -H "Depth: 1" -X PROPFIND http://host/path. So if the webdav share is under some path like http://host/dav i think you need to use prefix /dav to get the webdav server know how to produce URL:s

Maybe it's worth trying with webdav client that is known to work first? think i've used macOS finder and kodi.

from caddy-webdav.

I found a workaround with finder:
https://webdav.danobe.dev:6180

with config:

{
        order webdav before file_server
}

webdav.danobe.dev:6180 {
        basicauth {
                user $2a$14$9SMz8Yufvqjm03TuaBvesecPC9/pnE11hQh3YpLUkMG8XCP2Sr4GG
        }
        webdav {
                root /webdav
        }
        file_server
}

will work in finder, but not in Rider.
The difference is Rider uses dav:// and in finder it doesn't work with dav:// prefix but with the https:// prefix...

Anyone an idea what I do wrong here? why does it work with https as prefix?
The problem in Rider is, I can't change the dav:// prefix to https:// because it inserts it automatically ...

Googleing the problem also had no answer for me.

Thank you @wader for your input with Finder, that was a good idea! :)

from caddy-webdav.

Hi Daniel, I'm sorry to say I don't actually know much about this setup. What errors are you getting?

I've read this here, and here it get's shown I have to create a password hash, but I don't know if this is necessary?

It's recommended to use some form of authentication if you're enabling this on a public network interface, yes. basicauth is probably the easiest way to do it. This docs page can help: https://caddyserver.com/docs/caddyfile/directives/basicauth

from caddy-webdav.

Hi, i would probably try without auth just to make sure then look into if prefix is needed. Looking at the above screenshot i suspect you might want prefix /dav? see the documentation about prefix for details

from caddy-webdav.

webdav.danobe.dev:6180 {
        #root /webdav
        basicauth {
                user $2a$14$9SMz8Yufvqjm03TuaBvesecPC9/pnE11hQh3YpLUkMG8XCP2Sr4GG
        }
        webdav {
                root /webdav
                #prefix /webdav
        }
        #webdav
        file_server
}

authentification works as expected.
Should this be the expected output, if you open it in chrome the site?

<D:multistatus xmlns:D="DAV:">
<D:response>
<D:href>/</D:href>
<D:propstat>
<D:prop>
<D:resourcetype>
<D:collection xmlns:D="DAV:"/>
</D:resourcetype>
<D:displayname/>
<D:getlastmodified>Thu, 17 Aug 2023 18:30:39 GMT</D:getlastmodified>
<D:supportedlock>
<D:lockentry xmlns:D="DAV:">
<D:lockscope>
<D:exclusive/>
</D:lockscope>
<D:locktype>
<D:write/>
</D:locktype>
</D:lockentry>
</D:supportedlock>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>

Because in chrome I get a response from the site ...
Not sure is this is what I would expect due to no experience regarding webdav ...

Kind regards

from caddy-webdav.

@DanielOberlechner I'm guessing the dav prefix doesn't use TLS? Whereas HTTPS is just webdav HTTP requests over TLS? Quick googling suggests Rider may not support WebDAV over TLS (but it does support FTP over TLS)...

from caddy-webdav.

Hi @mholt,
thank you for answering!

I got the message:
"Unknown message with code webdav.danobe.dev:6180 failed to respond"

This is my Caddy config:

{
        order webdav before file_server
}


webdav.danobe.dev:6180 {
        root * /webdav
        basicauth {
                user $2a$14$9SMz8Yufvqjm03TuaBvesecPC9/pnE11hQh3YpLUkMG8XCP2Sr4GG
        }
        webdav
}

Ports are open and forwarded...

Any suggestions on how to fix or what I do wrong?

Kind regards,
Daniel Oberlechner

from caddy-webdav.