-
Notifications
You must be signed in to change notification settings - Fork 184
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
[Capabilities] Expiration date for public links inconsistent #4445
Comments
Missing feature, non relevant for GA. @michaelstingl what#s the impact for the desktop client? |
It's causing #4380 . I assume it's really minimal effort to improve things for the desktop client. |
IMO it would be easier and cleaner to add the expiration to the capabilities instead of building a workaround in the client... isn't it just a matter of adding a hardcoded value to the capabilities? |
I assume it's hardcoded in the capabilities, but it shouldn't be there. Just remove |
@pmaier1 could you have another look into it. Looks like a one liner. Thanks |
Ahh, so this is not about the default expiration date feature but only about capabilities. Then this is good to go, of course. |
To my understanding the default expiration date handling only ever happens in the clients anyway. The backend always expects either no expiration or an actual expiration date. |
|
In oC10, as an admin you can set a default expiration date and you can enforce that, so that users cannot exceed it and have to set it. That's not available in oCIS currently. I thought the question here is about those. |
Ah ok. Indeed, the issue was never about enforcing the expiration. Only about the default amount of days (for clients to determine the default expiration date upon creation of the public link). |
Yeah, and there is no default for that in oCIS currently afaik. |
Providing a default for clients in the capabilities should have been sufficient for that. As far as I understood there is no handling of default expiration days needed in the backend (might be wrong). But disabling the default expiration is the safe bet. That's being done in #4475 now |
Describe the bug
oCIS capabilities have
"expire_date" > "enabled": true
, but no"days": "7",
are set. This confuses the 2.11 desktop sync clients.oCIS
curl request + response
oC10 with expiration date disabled
curl request + response
oC10 with expiration date enabled
curl request + response
Setup
https://ocis.owncloud.com
@dragotin FYI
The text was updated successfully, but these errors were encountered: