Probably relates to #34971

Previously on creation of a public link share, if "Set default expiration date" was enabled and no expire data parameter was set on the share creation API request, the server would automatically set the default expiration date on share creation.

Now, it does not do that anymore and instead replies "Expiration date is enforced".

This breaks how the desktop client used the API. In particular it will make it impossible to create any public link shares on desktop clients before 2.6.0 if "Enforce expiration date" is also enabled.

See owncloud/client#7245

Possibly the link share creation API could distinguish between

• requesting "no expiry" (to resolve the problem PR [stable10] Fix public link share default expiration behavior #34971 was addressing)
• requesting "expire at that date"
• not having the "expireDate" parameter at all (restoring the previous behavior for this case)