Accessing shared resource can be done using either mount share id or virtual share id.

[PrajwolAmatya]

In spaces dav version, when sending API request, the endpoint can either use mount share id as https://localhost:9200/remote.php/dav/spaces/<mount-share-id> or we can use virtual share id as https://localhost:9200/remote.php/dav/spaces/<virtual-share-id>/<resource-name>. In both cases, we can access the shared resources.

We have multiple scenarios where we need to access the shared resources. In those scenarios, what should we prefer mount-share-id or virtual share id, for test cases or should we test for both mount share id or virtual share id?

Related:

• copy to overwrite (file and folder) from Personal to Shares Jail behaves differently #4393
• Add preview tests coverage for space dav version #6752

CC @individual-it @phil-davis @ScharfViktor @micbar @saw-jan

[ScharfViktor]

web uses https://localhost:9200/remote.php/dav/spaces/<mount-share-id>

look here

let have test for that IMHO

or add new path to our collection of path

[PrajwolAmatya]

With the discussion of this issue, we used the mount-shared-id to access the shared resources. The test has been covered in the PR #7234. So, closing this issue as completed.