Hi Steve, Thank you very much for your reply. We actually could solve it yesterday, a short while after I sent the e-mail. What we did was change the tag ENFORCE_MODE to permit-all-requests, in fedora.fcfg. it seem to be working now. Thanks again for your help. Filipe
Citando Steve Bayliss <[email protected]>: > Hi Luis > > It sound like you have hit this issue: > https://jira.duraspace.org/browse/FCREPO-703 > > This is a known problem in Fedora 3.3 which has been resolved in Fedora 3.4. > > The work-arounds for this (see the JIRA issue) are to modify your > fedora.fcfg: > > - disable datastream filenames in the content-disposition header > -- set the parameter "datastreamContentDispositionInlineEnabled" to "false" > in fedora.fcfg; or > > or > > - set the datastream filename for the content-disposition header to be the > datastream ID by default > -- set the parameter "datastreamFilenameSource" to "id" (the default value > is "rels label id" > > Regards > Steve > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: 08 September 2010 11:05 > To: [email protected] > Subject: [fcrepo-user] FedoraCommons3.3 - problem acessing object > datastreams > > > Hi everyone, > > We have a problem with our installation of fedora commons 3.3, when we > access as object, such as fedora-system:ContentModel-3.0, and then try > to access the datastreams, following the "View the Datastreams List > for this Object" link, in this case we obtain (after login), 3 > datastreams, which IDs are: > > DC, > RELS-EXT, > DC-COMPOSITE-MODEL > > When we try to access any of the datastreams, we get the following > error message: > > HTTP Status 401 - > > type Status report > > message > > description This request requires HTTP authentication (). > > We can access the datastreams from within the fedora admin application > and we have another installation of Fedora Commons 2.2.2 and we can > access the datastreams there too. > > So we don't know what is the problem. > > Does anyone have any idea of what the problem might be? > > We have stumbled upon this problem when trying to migrate the objects > from FC2.2.2 to FC3.3. We thought it was a problem of the migration > process, but then we realized we had this problem right after > installation with the objects already contained there. > > Thanks > Best regards > > Luis Filipe Lopes > FCUL > Portugal > > > ---------------------------------------------------------------------------- > -- > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Fedora-commons-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > > ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
