sharee (editor role) MOVE a file by file-id into Personal space responds with 502 instead of 403

[saw-jan]

Describe the bug

When a sharee with editor role tries to MOVE a file by file-id as a source into the Personal space root as the destination, the server responds with 502 but it should be 403 like while using file-path.

Trying with sharee with viewer role returns 403.

Steps to reproduce

1. editor role ❌

curl -XMOVE "https://localhost:9200/remote.php/dav/spaces/<file-id>" \             
-H"Destination: https://localhost:9200/remote.php/dav/spaces/<demo-personal-space-id>/file.txt" \
-udemo:demo -vk

2. viewer role 👍

curl -XMOVE "https://localhost:9200/remote.php/dav/spaces/<file-id>" \             
-H"Destination: https://localhost:9200/remote.php/dav/spaces/<demo-personal-space-id>/file.txt" \
-udemo:demo -vk

Expected behavior

< HTTP/1.1 403 Forbidden

<?xml version="1.0" encoding="UTF-8"?>
<d:error
	xmlns:d="DAV"
	xmlns:s="http://sabredav.org/ns">
	<s:exception>Sabre\DAV\Exception\Forbidden</s:exception>
	<s:message>move: error: permission denied: %file-id-here%</s:message>
</d:error>

Actual behavior

< HTTP/1.1 502 Bad Gateway
<
<?xml version="1.0" encoding="UTF-8"?>
<d:error
	xmlns:d="DAV"
	xmlns:s="http://sabredav.org/ns">
	<s:exception></s:exception>
	<s:message>move:error: not supported: cannot move across spaces</s:message>
</d:error>

[saw-jan]

As per #8063 (comment), #8063 (comment) and #4087 (comment), the 502 statuscode is the correct code that server should respond. So closing this.