When a client call a PROPPATCH method, it retrieves a 405.
This occurs when Windows native client tries to copy a file on a remote. After calling a HEAD and a PUT, it calls a PROPPATCH. As the server replies with a 405, the client decides to rollback and DELETE the file.
When doing the same sequence on a Tuleap 12.3, the PROPPATCH returns 207, and the copy operation succeed.