------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev_______________________________________________ Fedora-commons-users mailing list Fedora-com...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
Hi Janna
Re-reading, I was a little confused by this behaviour. If you haven't modified deny-unallowed-file-resolution.xml (or implemented access to files in some other policy), then ingesting with M datastreams with contentLocations specified as file:/// should simply fail, whatever the datastream ID.
Attempting to reproduce here, ingesting DC_TEST as "M" with a file:/// protocol did indeed fail here. However updating that policy to allow the file resolution, the ingest succeed.After updating the policy, I am able to reproduce the bug with DC: It seems that the content of DC is read during the ingest (to check eg for dc:identifier, and add if not present) - however the auth is not being passed through whilst reading the file content, so it fails.I have raised https://jira.duraspace.org/browse/FCREPO-823 for this.