-
Notifications
You must be signed in to change notification settings - Fork 663
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
OC9.0 will come with an additional WebDAV endpoint .... #4007
Comments
... more resources will come |
Return it as part of the capabilities call then we try to favor it over the default endpoint? |
In the first place I need this as a config option to some degree to start testing the endpoint. The decision to enable it could be done on server version at the end from my understanding |
It can be configured in the theme already (in Theme::webDavPath). Is that enough for you? |
using a theme will not work because I don't want to maintain my own branded client build. |
If this helps you - sure - why not |
The new webdav endpoint will contain the user name, or rather the principal. That is not neccessarily the user. That means that the client needs to query the principal at startup, before accessing any webdav resources. The server provides an OCS call to query the principal. |
Need to add to this issue: @dragotin for additional technical details please. |
By now, the branch with the new server implementation was not yet merged, and its not sure if it will for 9.0. |
Branch is not merged, milestone removed. |
Status: (AFAIK) Waiting for server capability returned |
@ogoffart How is this issue vs the new chunking? |
The rules to select the webdav url are now: - If the server reports that the new chunking algorithm is working, always use remote.php/dav/files/<username> This capability can be overriden with an environment variable - Otherwise, use the dav path provided by the theme, which defaults to remote.php/webdav This means that with the newer server, the branding can no longer override the webdav URL. If there is still an usecase for the branding to do so, we need to find another way to override it. But it is now more complicated to configure as might need include the username and need different endpoint depending on the operations (chunks or not) Issue #4007
The rules to select the webdav url are now: - If the server reports that the new chunking algorithm is working, always use remote.php/dav/files/<username> This capability can be overriden with an environment variable - Otherwise, use the dav path provided by the theme, which defaults to remote.php/webdav This means that with the newer server, the branding can no longer override the webdav URL. If there is still an usecase for the branding to do so, we need to find another way to override it. But it is now more complicated to configure as might need include the username and need different endpoint depending on the operations (chunks or not) Issue #4007
#5332 has been merged. |
..... which would be great if the client could make use of.
The text was updated successfully, but these errors were encountered: