Closed ghost closed 3 years ago
Haven't tried but maybe you could somehow combine method GET { ... }
and {http.matchers.file.type}
to make browse
handle those request? I think that should be fine as WebDAV useu PROPLIST
method for directories.
Using matchers is probably the way to go.
@JaydenMcEncroe This may work for you. (Untested)
localhost:80 {
@notget {
not method GET
}
root * /www
file_server browse
webdav @notget
}
With the proper order it works, thanks!
{
order webdav before file_server
}
localhost
@notget {
not method GET
}
root * /www
webdav @notget
file_server browse
Or alternatively, for a public listing, but authenticated dav:
localhost
root * /www
@notget {
not method GET
}
route @notget {
basicauth {
davuser JDJhJDE0JGJXeGVmeHgzUmREVFc0dHpFbUZEaC5ZYW5QemVLVXBxUUtGLkpRSUxveDVRRE9pbVVNTGNL
}
webdav
}
file_server browse
Based on the documents and my test, it seems like WebDAV has to be served in a different path with directory listing, one cannot have them both functioning under the same path, is that correct?
As an Apache & Nginx user, I felt quite surprised, as it is an expected behaviour to have them working in the same path.
Cheers, Jayden