Homeserver webdav

[dzdidi]

Implement webdav compatible routes on homeserver.

This will allow users to use available webdav compatible clients like https://cyberduck.io/ to access and explore their files on their homeserver.

This is already implemetend for admin server of the homeserver with HTTP Basic authentication

Initial change should ideally be compatible with current authentication scheme. As possible temporal work around would be to put session_id into http authorization header for compatibility

[dzdidi]

I am working on it in this branch #224
It also includes some clean ups and restructuring of the code

[dzdidi]

Interesting finding which might significantly affect scope of the change:
Cyberduck is supported only for Windows and MacOS. Linux supports WebDAV basically in it File Explorers: GNOME Files, Nautilus etc. Which results in fact that there basically no other clients.

The problem however is that Linux based clients accepts URLs only with dav / davs protocols :( this implies that to allow this functionality for Linux users we need to run corresponding endpoints not on HTTP server but on DAV servers.

As of now I do not see how to make axum work with other protocol than HTTP. Axum itself is based tower (or tower-http). I am looking if it is possible to make tower work with different application level protocol.

If there is no easy way, I think we can stay with http:// for a time being and move to dav:// later

[dzdidi]

https://github.com/fstanis/awesome-webdav - list of handy webdav tools

From the desktop apps for linux https://www.crossftp.com/ - works with current implementation. However the authentication methods are password basic authentication, server cert, client cert, and Kerbros.

cross platform cli tool https://rclone.org/ works with current implementation. Also supports Bearer Auth