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
expireDate can be specified in any date-time format #36558
Comments
I am asking this because, if we keep allowing the extended behaviour to work, then there might be some clients that (maybe unintentionally) use it - send Once clients are using the flexibility, then we will need to retain it on other server implementations (e.g. OCIS) @micbar @PVince81 @DeepDiver1975 or whoever should have an opinion. |
I added this to 10.4.0 project so we discuss it along with the user-group-share-expiry review. |
@pmaier1 @phil-davis @felixheidecke @jvillafanez Let us sit together. |
From my point of view, "YYYY-MM-DD" is the one that is officially supported. The rest isn't officially supported (unless @pmaier1 says otherwise) and they're in a "use it at your own risk if it works" state, so if something breaks, you've been warned. |
Any more opinions? |
We can leave the ticket open. It's something to discuss if we want to enforce an specific format or not, but I don't think it's a priority at the moment. |
I remved from the 10.4 project, because this is now a discussion issue and not to be "finished" for 10.4 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed. |
When using the sharing API and sending
expireDate
in a request to create/modify a share, the documentation https://doc.owncloud.com/server/developer_manual/core/apis/ocs-share-api.html#create-a-new-share says:But if you send the
expireDate
in any format that https://www.php.net/manual/en/function.strtotime.php understands, then that also works - e.g.+3 days
or01/02/2020
We are adding a feature to have expiry dates for user and group shares. The feature PR also behaves like this, allowing an extensive range of ways to send
expireDate
Is it OK that this extended behaviour works?
The text was updated successfully, but these errors were encountered: