Skip to content
This repository was archived by the owner on Jun 5, 2024. It is now read-only.

Drop support for webdav v1 #958

Closed
kulmann opened this issue Jan 24, 2022 · 12 comments · Fixed by #962
Closed

Drop support for webdav v1 #958

kulmann opened this issue Jan 24, 2022 · 12 comments · Fixed by #962

Comments

@kulmann
Copy link
Contributor

kulmann commented Jan 24, 2022

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.

@kulmann
Copy link
Contributor Author

kulmann commented Jan 24, 2022

cc @rpocklin

@kulmann
Copy link
Contributor Author

kulmann commented Jan 24, 2022

cc @phil-davis @individual-it

@phil-davis
Copy link
Contributor

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.

@fschade
Copy link
Contributor

fschade commented Jan 24, 2022

Is there a reason why ownCloud classic still supports webdav (v1)?
If i get it right dav (v2) has the same set of features!?

So if we do not miss something i vote to drop it.

@DeepDiver1975
Copy link
Member

v1 only serves the files of the currently logged in user
v1 serves files, calendar, contacts, trashbin and many more following the URI principle that URIs are truly unique ...

remote.php/webdav/welcome.txt is not unique as it depends on the logged in user
remote.php/dav/files/alice/welcome.txt in contrary is unique

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 ...

@DeepDiver1975
Copy link
Member

So if we do not miss something i vote to drop it.

from the sdk perspective there is no reason to stay with v1 - it should have been used right from the beginning 🙈

@AlexAndBear
Copy link

AlexAndBear commented Jan 24, 2022

@DeepDiver1975 Thx, we proceed replacing v1 with v2

@butonic
Copy link
Member

butonic commented Jan 24, 2022

Um, might be needed for cernbox @kulmann

@AlexAndBear
Copy link

@butonic But if we release a new major version, this might ain’t an issue ?

@pascalwengerter
Copy link
Contributor

@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 :)

@kulmann
Copy link
Contributor Author

kulmann commented Jan 24, 2022

Um, might be needed for cernbox @kulmann

@diocas @elizavetaRa do you maybe know?

@diocas
Copy link
Contributor

diocas commented Jan 24, 2022

For CERNBox should not matter, assuming that OCIS has the correct implementation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants