It looks like running jfrog directly might fail on some tests, I will attempt to reconfigure jfrog later.

It looks like running jfrog directly might fail on some tests, I will attempt to reconfigure jfrog later.

It could also be problems of opendal itself.

For example, jfrog returns 200 for rename success:

Unexpected (persistent) at rename, context: { uri: http://127.0.0.1:8081/artifactory/example-repo-local/4b4169a6-08ff-40e1-907b-f07deccd5e67/b95cf5c9-e399-40a4-af59-20760ece910d, response: Parts { status: 200, version: HTTP/1.1, headers: {"x-jfrog-version": "Artifactory/7.77.5 77705900", "x-artifactory-id": "e44bf43451c1c186:-1fcda5a9:18de38a6cca:-8000", "x-artifactory-node-id": "062242c5aed1", "transfer-encoding": "chunked", "date": "Mon, 26 Feb 2024 03:53:58 GMT"} }, service: webdav, from: b95cf5c9-e399-40a4-af59-20760ece910d, to: e265191f-bca1-412e-9874-b824789e035a/8b0aa2ba-1d41-4782-9584-8eb83c286629/c819085a-672e-45ff-b426-67d77bd45627 }

We should allow it.

Ok, I found something really interesting...

In XML, content such as &xxxx; is considered escaped content and is treated specially. For example, & becomes & and " becomes ". The library quick-xml converts these escaped characters back into their original form during deserialization.

However, we encountered a test case containing the sequence &()_+-=;, which quick-xml fails to recognize.

Ok, I found something really interesting...

I created an issue at upstream tafia/quick-xml#719, we can workaround it first.

Hi, @zjregee, thanks a lot for your contribution! I jumped into this PR because I found something very odd that makes debugging it quite tedious. I hope you don't feel like you're wasting your time.

Most webdav issues have been fixed now, we can move forward!

Thanks a lot for your help, it looks like things are working out!