-
Notifications
You must be signed in to change notification settings - Fork 2.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] Wrong MOVE requests deletes directory #5777
Comments
If I remember correctly, oC implements MOVE as COPY+DELETE.. Maybe there is some wrong error checking there. |
This is easy to reproduce with the MOVE of death:
|
reproduced - preparing a fix .... |
As far as I can tell SabreDAV is deleting the destination folder because it exists There is a check above to prevent source and destination being identical - the code comment is a bit unclear: @evert in the master branch I see an additional check which seems to be missing in the 1.7 code base Or did I miss anything? THX |
You're right. This was fixed on dev-master, but didn't seem like a priority to backport, because it would only affect broken clients. |
@dragotin I'll move this to oc7 |
Is this still an issue ? We seem to have upgraded to Sabre 1.7.11 on master. |
Yes, quick check with master works as expected. I think we can close this one. |
Current master (near ownCloud 6.0.0 beta3) has the following problem:
During client development the client issued the this request:
and the reply was
which seems to correct.
The problem with that is only that after this request, the directory slot4 is completely gone on the server.
At the same time, apache's error log shows
This is a severe problem because it means data loss, even if the WebDAV request might be bogus.
The text was updated successfully, but these errors were encountered: