DuraCloud Release 2.1 : Known Issues

The following issues are known to exist in release 2.1.0 of DuraCloud:

Title

Issue

Tracker Item

Work Around

Incorrect redirects from HTTP to HTTPS

When performing PUT/POST/DELETE requests via the REST API, if the URL uses http:// rather than https:// the response is a 404.

DURACLOUD-255

Use https:// when performing requests via the REST API of hosted DuraCloud instances

Incorrect MIME types set on files

When uploading files via the sync tool which do not have an extension, the MIME type is always set to application/octet-stream

DURACLOUD-227

Set the MIME type of these files either through DurAdmin or via the REST API

Administrative files in storage report graphs

The storage report information displays all files in DuraCloud, including all of the administrative files

DURACLOUD-514

View reports for content spaces directly

Sync Tool and Java 7

When running the Sync Tool with Java 7, errors indicating "peer not authenticated" or "unrecognized_name" may occur. This is due to a changed requirement in Java 7.

DURACLOUD-717

Use the flag: "-Djsse.enableSNIExtension=false" when running the Sync Tool

More issues and planned improvements can be found on the DuraCloud issue tracker.