We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some WebDAV implementations seem to use displayName in their XML response instead of the more common displayname key.
displayName
displayname
<d:multistatus xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns" xmlns:nc="http://nextcloud.org/ns" xmlns:x1="http://open-collaboration-services.org/ns"> <d:response> <d:href>/dav.php/@Home/new_library/</d:href> <d:propstat> <d:prop> <d:displayName>new_library</d:displayName> <d:getetag>80a1745cfaa43b2057f781413209ff90</d:getetag> <d:getlastmodified>Tue, 22 Aug 2023 08:10:49 GMT</d:getlastmodified> <d:creationdate>2023-08-22T10:10:49+02:00</d:creationdate> <oc:id>02320738</oc:id> <d:resourcetype> <d:collection/> </d:resourcetype> <d:iscollection>1</d:iscollection> <d:isFolder>t</d:isFolder> <oc:permissions>RGDNVCK</oc:permissions> <x1:share-permissions>31</x1:share-permissions> </d:prop> <d:status>HTTP/1.1 200 OK</d:status> </d:propstat> </d:response> </d:multistatus>
The text was updated successfully, but these errors were encountered:
Fix ezhov-evgeny#137 - Try different cases for displayName, also allo…
1799a36
…ws other keys to be under different names if required in the future
Successfully merging a pull request may close this issue.
Some WebDAV implementations seem to use
displayName
in their XML response instead of the more commondisplayname
key.The text was updated successfully, but these errors were encountered: