Conversation
|
Yes the share expired after the specific date but not at 0:01. He expires when the ExpireShareJob runs which can be at any time on the following day. |
|
@NannaBarz that was also fixed some time ago. Whenever a share is attempted to be accessed, the server validates the access attempt in real-time. If it is after the end of the expiration date (at 00:00:01 and after on the next day) the server removes the share in real-time and responds to the request with 404 "not found". If you can demonstrate that this does not work correctly on ownCloud core 10.8.0 onwards, then please raise an issue. |
|
Could a clarifying statement be made if the revert is valid or not so we can proceed? |
|
I believe that, in current oC10 releases, shares correctly stop working at the end of the expiration date. That is what the original text said. If someone can show that there is a problem, then please give a scenario of steps to demonstrate the problem - then we can write some text about what the problem is, get it fixed in the next release,... |
PR owncloud/core#38775 fixed this behavior, released in ownCloud core 10.8.0.
The ExpireSharesJob now correctly only removes shares that have an expiration date of yesterday or before. Shares that expire on the current day are left in-place, because they need to work until the very end of the day.
So, IMO, the previous text was correct.