-
Notifications
You must be signed in to change notification settings - Fork 33
Drop support for webdav v1 #958
Comments
cc @rpocklin |
I don't see a problem with that. All server implementations have the "new" webdav v2. So clients and client infrastructure does not have to know anything about "old" webdav v1. |
Is there a reason why ownCloud classic still supports webdav (v1)? So if we do not miss something i vote to drop it. |
v1 only serves the files of the currently logged in user remote.php/webdav/welcome.txt is not unique as it depends on the logged in user the over all plan was once to even allow cross-user operations like copying files from one user space to another .... but we never got there ... |
from the sdk perspective there is no reason to stay with v1 - it should have been used right from the beginning 🙈 |
@DeepDiver1975 Thx, we proceed replacing v1 with v2 |
Um, might be needed for cernbox @kulmann |
@butonic But if we release a new major version, this might ain’t an issue ? |
We should switch the whole thing over to the way we do semver in the other web-related repos I suggest :) |
@diocas @elizavetaRa do you maybe know? |
For CERNBox should not matter, assuming that OCIS has the correct implementation. |
We're currently planning to drop support for webdav (v1) in favour of the new dav implementation (v2), which is fully supported by both ownCloud 10 and ownCloud Infinite Scale.
Would like to hear if there are objections to this.
The text was updated successfully, but these errors were encountered: