Use the user in request for deciding the layout for non-home DAV requests #1401
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the incoming
/dav/files/userID
requests, we have different namespaces depending on whether the request is for the logged-in user's namespace or not. Since in the storage drivers, we specify the layout depending only on the user whose resources are to be accessed, this fails when a user wants to access another user's namespace when the storage provider depends on the logged in user's namespace.For example, consider the following case. The owncloud fs uses a layout
{{substr 0 1 .Username}}/{{.Username}}
and it's mounted at/users
. The user einstein sends a request to access a resource shared with him, say/dav/files/marie/abcd
, which should be allowed. However, based on the way we applied the layout, this can only be translated to/users/e/marie/abcd
.Fixes #1215