fix the resource name

[2403905]

Description

After the sharer changed the name of a shared resource, the receiver can see the new name, but cannot access it by using the new name.
We fixed a problem where after renaming the resource as sharer the receiver saw a new name.

Related Issue

• Fixes after renaming resource as sharer the receiver cannot access it by WebDAV using the new name #8242
• Related changes https://github.com/cs3org/reva/pull/4463/files

Motivation and Context

How Has This Been Tested?

• test environment:

1. create a folder
2. share the folder
3. as sharer rename the folder
4. as receiver do a propfind on the share-jail curl -XPROPFIND -uuu1:uu1 'https://localhost:9200/dav/spaces/a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668' -k | xmllint --format -

Expected behavior

d:href element and oc:name should correlate

Actual behavior

d:href, d:displayname and oc:name shows the old name for receiver

response (shortened)

 <d:response>
    <d:href>/dav/spaces/a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668/folder/</d:href>
    <d:propstat>
      <d:prop>
        <oc:name>folder</oc:name>
        <d:displayname>folder</d:displayname>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
  </d:response>

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[kobergj]

Looks good but needs a reva bump

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

Reva bumped <3