Thanks, that worked perfectly. On Tuesday, August 30, 2022 at 8:30:47 PM UTC+5:30 Tim Donohue wrote:
> I see... > > It appears that xmlui.content_disposition_threshold needs to be a valid > integer...which means it'd have a maximum value of 2147483647 > <(214)%20748-3647> (roughly 2GB). > > So, you could try that value, but it won't work for PDFs >2GB > obviously....those will still be downloaded instead. > > Looking at the code, you also could try setting it to "0" (instead of > "-1"). It appears zero may be another way of trying to disable it. But, > I'm not entirely sure if that'd work. > > If neither of these options work, then I think your best bet may be to > look towards an upgrade to DSpace 7 in the future (6.x will be EOL as of > July 2023 & may not have any additional releases after 6.4). DSpace 7 will > attempt to serve *everything *in "inline" mode as long as the file format > is included in the "Accept" header (which should include all the formats > that your browser understands). > > Tim > > ------------------------------ > *From:* [email protected] <[email protected]> on behalf > of [email protected] <[email protected]> > *Sent:* Monday, August 29, 2022 9:37 PM > > *To:* DSpace Technical Support <[email protected]> > *Subject:* Re: [dspace-tech] Re: Content Inline Disposition Threshold > Dspace 6.3 > > Yes, I did set xmlui.content_disposition_threshold = -1. That didn't work. > My pdfs are around 2.5 GB, so I tried setting a large value like > 3300000000 since 3 GB =3221225472 > The error message when trying to open the bitstream: > java.lang.NumberFormatException: For input string: "3300000000". > > > On Tuesday, August 30, 2022 at 12:58:13 AM UTC+5:30 Tim Donohue wrote: > > Hi, > > Oh, I missed that you mentioned XMLUI. I think the XMLUI property is > named "xmlui.content_disposition_threshold" instead. If the -1 value isn't > working, you can also try setting it to a very large number... as see there > were some prior reports that some people couldn't get -1 to work for XMLUI > here: > https://groups.google.com/g/dspace-community/c/hZgtgCsVh-A/m/I4mHhm2XCQAJ > > Tim > ------------------------------ > *From:* [email protected] <[email protected]> on behalf > of [email protected] <[email protected]> > *Sent:* Monday, August 29, 2022 12:38 PM > *To:* DSpace Technical Support <[email protected]> > *Subject:* [dspace-tech] Re: Content Inline Disposition Threshold Dspace > 6.3 > > So the same browser which understands the formats in jspui for > "webui.content_disposition_threshold = -1" and opens the file "inline", > does not do so in xmlui?? > > On Monday, August 29, 2022 at 9:00:47 PM UTC+5:30 Tim Donohue wrote: > > In DSpace 6, setting "webui.content_disposition_threshold = -1" just tells > DSpace to serve all files "inline" (which tells your browser to attempt to > view it in the browser). However, if your browser doesn't understand the > format, then it's still possible it'll simply download the file. DSpace > cannot control what formats your browser understands, so there's no way to > force all files to open in your browser. > > For more information on what "inline" Content Disposition means, see this: > https://stackoverflow.com/questions/1395151/content-dispositionwhat-are-the-differences-between-inline-and-attachment > > > If you have more questions, let us know on this list. > > Tim > > On Saturday, August 27, 2022 at 4:34:31 AM UTC-5 [email protected] > wrote: > > Any help here? > > On Friday, August 26, 2022 at 1:55:01 PM UTC+5:30 [email protected] > wrote: > > Why Content Inline Disposition Threshold is not working in spite of > putting the value=-1 for xmlui? > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/f162465c-90d4-4fec-8099-6f7be32bcb1bn%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-tech/f162465c-90d4-4fec-8099-6f7be32bcb1bn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/87401de8-20ac-4cf5-a160-3524cd724003n%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-tech/87401de8-20ac-4cf5-a160-3524cd724003n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/31587850-6548-4ba7-83cd-04238c3dad8en%40googlegroups.com.
