Using nzbDAV directly as a webDAV in Infuse/Vidhub

[evanesce345]

Hey first of all love the app. I don't have any of the arr stack set up at the moment, so I've just been using nzbdav with AIOStreams and Stremio currently.

I figured I would try to use the webDAV server on media players like Vidhub and Infuse to add my nzbs to my library, and for Vidhub it works really well. Infuse, however, doesn't read the filesystem well. When I add the server to the app it doesn't treat the folders as being accessible / think they are folders at all:

I thought maybe since the files are nested down /content/Movies then I could specify that path and replicate the way it works with TorBox in the app so each movie has its own folder like so:

Yet the folders are still inaccessible. Unless I specify the path to an individual mkv file, it doesn't work, which of course isn't a solution. And since it works flawlessly on Vidhub I imagine it's an Infuse specific issue. Before I go and ask them about it though, is there any idea why this would be happening? Thanks.

[nzbdav-dev]

I unfortunately do not have an Apple TV, and have never used infused (apologies!).
Maybe someone else can shed some light?

[dumpemout]

Having the same issues... here's what my server's logs are showing. I think infuse is enforcing strict PROPFIND compliance for the getcontentlength and iscollection requests. My logs are showing those methods aren't supported and I'm guessing Infuse is just assuming the folder is a file by default.

[07:17:18 WRN] Property {DAV: }getcontentlength is not supported on item Movies.

[07:17:18 WRN] Property {DAV:}iscollection is not supported on item Movies.