You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the first implementation the direct download link (for s3 and swift backends) will contain an link to the owncloud instance itself which will generate a temporary/one time access token.
The final target url will be generated and returned as redirect to the client - the client will follow the redirect accordingly.
Furthermore in case the redirected url is unreachable or the owncloud server returns with an error (e.g. token could not be generated) the client shall fallback to the regular webdav based download.
This approach will work as long as tokens can be generated.
There is no need to add any additional libraries in the client.
We have to think about a solution for systems where no token can be generated (for whatever reason).
In the first implementation the direct download link (for s3 and swift backends) will contain an link to the owncloud instance itself which will generate a temporary/one time access token.
Sample direct download url
The final target url will be generated and returned as redirect to the client - the client will follow the redirect accordingly.
Furthermore in case the redirected url is unreachable or the owncloud server returns with an error (e.g. token could not be generated) the client shall fallback to the regular webdav based download.
This approach will work as long as tokens can be generated.
There is no need to add any additional libraries in the client.
We have to think about a solution for systems where no token can be generated (for whatever reason).
let's generate explicit tickets now for
The text was updated successfully, but these errors were encountered: