This page last changed on Sep 30, 2011 by bbranan.
The following issues are known to exist in release 1.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 |
Bulk Image Transformer converting from JP2 |
The Bulk Image Transformer has seen failures when converting JP2 files into other formats |
DURACLOUD-345 |
Use a larger type and/or number of servers for this type of job |
Incorrect format indicated for service output files |
The output files generated by DuraCloud services indicate that they are comma-separated value files, when they are actually the tab-separated value format |
DURACLOUD-516 |
Handle service output files as tab-separated |
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 |
Service failures vs. failures in results |
DuraCloud services currently indicate that a service has "failed" when the service ran properly to completion, but the results include an anomaly |
DURACLOUD-512 |
Look closely at any reported service failure do determine its cause |
More issues and planned improvements can be found on the DuraCloud issue tracker.
|