Some progress has been made:
The reason for some files and folders not being displayed is a bug in PROPFIND implementation of "nginx-dav-ext-module"!!! Using the latest version in the "uri-encode" branch of their GIT-hub repository (https://github.com/semantico/nginx-dav-ext-module/tree/uri-encode) fixed that issue.
But MOVE and COPY are nginx native functions and these still misbehave. It seems to be a very similar problem to the one in "nginx-dav-ext-module". Please, could anyone fix that?
And there is another bug I observed in conjunction with "Netdrive": It's creating new folders with "MKCOL <foldername>" instead of "MKCOL <foldername>/". nginx however is very picky with that missing "/". The result is a "209" error ("conflicts"). Is that a bug of Netdrive? I don't know, but Netdrive is around for quite a while and nobody seems to have problems with creating folders. IMO a missing "/" should not cause complete failure, especially if the target MUST be a folder (MKCOL)! Is there a way to work this around in the nginx config file? Maybe by some rewrite rule?
best regards
ako673de
The reason for some files and folders not being displayed is a bug in PROPFIND implementation of "nginx-dav-ext-module"!!! Using the latest version in the "uri-encode" branch of their GIT-hub repository (https://github.com/semantico/nginx-dav-ext-module/tree/uri-encode) fixed that issue.
But MOVE and COPY are nginx native functions and these still misbehave. It seems to be a very similar problem to the one in "nginx-dav-ext-module". Please, could anyone fix that?
And there is another bug I observed in conjunction with "Netdrive": It's creating new folders with "MKCOL <foldername>" instead of "MKCOL <foldername>/". nginx however is very picky with that missing "/". The result is a "209" error ("conflicts"). Is that a bug of Netdrive? I don't know, but Netdrive is around for quite a while and nobody seems to have problems with creating folders. IMO a missing "/" should not cause complete failure, especially if the target MUST be a folder (MKCOL)! Is there a way to work this around in the nginx config file? Maybe by some rewrite rule?
best regards
ako673de