-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webdav search select displayname property returns http 404 #17778
Comments
Same in 16.0.4 |
Hmm. Has that worked before? The patch below will add the displayname. What would you expect as displayname? Filename with extension, filename without extension, relative path or something else?
|
cc @rullzer @icewind1991 @tobiasKaminsky as the dav experts ;) Any idea why displayname is not exposed? |
There is no other property which provies the file name, I would expect displayname to be the file name with extension. |
Same issue here... |
i run Nextcloud on version 18. |
Is this Issue still valid in NC21.0.2? If not, please close this issue. Thanks! :) |
Yes, this is still an issue. It would be great to have it fixed. And, in general, to make sure the WebDAV protocol is fully implemented. |
still an issue...fix would be great! |
It seems this issue also applies to |
In nextcloud-server 17.0.0.9, performing a webdav basicsearch with select "displayname" property results in a 404 for this property in the multistatus.
Search Body:
Response:
The text was updated successfully, but these errors were encountered: