WebServer.Files API returns 403 when child is forbidden

[jimmyca15]

When enumerating a directory with the WebFiles API (/api/webserver/files?parent.id={id}) it is possible to get a 403 error due to a child virtual directory having a path that is not allowed. This behavior differs from the Core Files API (/api/files?parent.id={id}) where enumerating a directory that has read access will never respond with a 403 error.

Proposal

When enumerating a directory with the webfiles API and the path of a child is not allowed, that child webfile resource will have a NULL file_info field. The API will not return 403 until that child is specifically requested (/api/webserver/files/{id})