Hi. I could not find documentation to PROPPATCH and looked up your t

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Hi @Chrakker, Thank you for clear deion of the issue. <p d

A new version with a fix is available in <a href="https://www.nuget.org/packages/WebDa

Using PROPPATCH with custom Properties (Nextcloud/owncloud) about webdavclient HOT 3 CLOSED

skazantsev commented on May 25, 2024

Using PROPPATCH with custom Properties (Nextcloud/owncloud)

from webdavclient.

Comments (3)

CSchmidtDD commented on May 25, 2024 1

Hi @skazantsev ,

thank you for your fast fix.
Am currently working with owncloud/nextcloud and this behaviour is a major QOL change for me and probably others as well that included your NuGet.
Very much appreciated, indeed!

from webdavclient.

skazantsev commented on May 25, 2024

Hi @Chrakker,

Thank you for clear description of the issue.

Unfortunately, it's a bug in the library.

When multiple properties are passed it generates multiple prop elements, which is incorrect:

<?xml version="1.0" encoding="utf-8"?>
<D:propertyupdate xmlns:D="DAV:" xmlns:te="http://example.com/" xmlns:oc="http://owncloud.org/ns" xmlns:nc="http://nextcloud.org/ns">
    <D:set>
        <D:prop>
            <te:uploader>chrakker</te:uploader>
        </D:prop>
        <D:prop>
            <te:vertragstyp>XYZ</te:vertragstyp>
        </D:prop>
        <D:prop>
            <te:loeschdatum>01012044</te:loeschdatum>
        </D:prop>
    </D:set>
</D:propertyupdate>

Looks like some WebDAV servers can handle it and set all properties but a correct request should look like:

<?xml version="1.0" encoding="utf-8"?>
<D:propertyupdate xmlns:D="DAV:" xmlns:te="http://example.com/" xmlns:oc="http://owncloud.org/ns" xmlns:nc="http://nextcloud.org/ns">
    <D:set>
        <D:prop>
            <te:uploader>chrakker</te:uploader>
            <te:vertragstyp>XYZ</te:vertragstyp>
            <te:loeschdatum>01012044</te:loeschdatum>
        </D:prop>
    </D:set>
</D:propertyupdate>