Fix fetching resources moved to the trash. This required a large-scale refactoring and assorted bug fixing that hopefully clears up the backend APIs. Major changes:
- ExternalAPI.getResourceAtPath() now requires the call site to explicitly mention whether it will consider a resource moved to the trash. Previously it would always ignore such resources....
fixed transaction error on concurrent deletes of files of the same folder, removal of file from folder happens by cascade
-Fix the URL of files & folders shared by user, when requested with a trailing slash in the URL-Use UTF-8 encoding when reading post contents
- Fix the URL of files & folders shared by others, when requested with a trailing slash in the URL.- Make sure file and folder URIs are properly encoded in trash, shared & others namespaces.
include tag url in users json response
Implement "empty trash" as a DELETE on the /trash namespace. Also, make sure that GETs on children of /trash get the error they deserve.
Add debugging info on failed Shibboleth authentications. That way the user can aid their IdP on resolving the problem.
fixed an infinite loop when source and target are the same folders
Partial revert of r18: don't encode the resource names, only the URIs.
Encode the nonce before using it, since the servler container decodes it automatically.
View revisions
Also available in: Atom