DSpace

Shane:

Yes, we encountered this problem as well with Firefox. Terry Reese 
from Oregon State told me that there was a patch posted sometime ago 
that forces the browser to initiate a download by setting the 
Content-Disposition header element rather than inline viewing if the 
file is over a specific file size.  The patch is found here:
<https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group_id=19984>https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group_id=19984

The patch sets the threshold to 20 MB.  I set our threshold to 5MB.

At 02:47 PM 1/29/2009, Shane Beers wrote:
>I'm going to guess this is related to the default functionality of how
>firefox opens PDFs, but I'll ask here anyway. The collection admin for
>a particular section of our IR wrote me saying that she was getting an
>error opening a PDF from the IR. She would get the error "The file is
>damaged and could not be repaired" from Adobe Acrobat. If she right
>clicked and saved as... to her computer and opened it it was fine. It
>also opened fine from IE. My guess is that Acrobat is trying to open
>the file before it has actually completed downloading. The file is
>27mb, so that could potentially be the issue.
>
>It works fine from my mac and firefox browser, however.
>
>Is this a problem anyone else has run into? If so, is it something
>that can be "fixed" from DSpace's end?
>
>Thanks.
>
>
>Shane Beers
>Digital Repository Services Librarian
>George Mason University
>sbeers@...
>http://mars.gmu.edu
>703-993-3742
>
>
>
>
>------------------------------------------------------------------------------
>This SF.net email is sponsored by:
>SourcForge Community
>SourceForge wants to tell your story.
>http://p.sf.net/sfu/sf-spreadtheword
>_______________________________________________
>DSpace-tech mailing list
>DSpace-tech@...
>https://lists.sourceforge.net/lists/listinfo/dspace-tech

***************************
George Kozak
Programmer/Analyst Specialist
Division of Library Information Technologies (DLIT), Digital Media Group
501 Olin Library
Cornell University
607-255-8924
***************************
gsk5@...

Hi Shane,

We've run into this issue as well.  It is indeed an issue with the browser
and not the pdf file itself.  I managed to find the solution on this list,
so I've included it below.

The patch described will force all large (over 20mb I think) bitstreams to
be downloaded as opposed to being viewed in the browser, so make sure that
behavior is acceptable.

------------------------------------------------
Daniel Mancusi
Digital Projects Technologist
Library and Information Technology
Bucknell University
(570)577-1046
------------------------------------------------

[Dspace-tech] Problem viewing PDFs with FirefoxFrom:
dspace-tech-bounces@... on behalf of Reese, Terry
[terry.reese@...]
Sent: Wednesday, October 03, 2007 10:20 AM
To: George Kozak; dspace-tech@...
Subject: Re: [Dspace-tech] Problem viewing PDFs with Firefox

I'm not sure what version of Dspace you are using, but there is a patch
for this.  You can find it here:
https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group
_id=19984.  The issue can be found in both browsers and as the patch
describes, is related to how many pdf viewers render the content inline
within the browser (though, truth be told, I've only ever seen this error
show up while using Adobe's Readers in FireFox -- which is why I switched
to the FoxIt PDF Readers long time ago).

--TR

*******************************************
Terry Reese
Cataloger for Networked Resources
Digital Production Unit Head
Oregon State University Libraries
Corvallis, OR  97331
tel: 541-737-6384
email: terry.reese@...
http: http://oregonstate.edu/~reeset
*******************************************


--------------------------------------------------------------------------
------
From: dspace-tech-bounces@... on behalf of George Kozak
Sent: Wed 10/3/2007 6:41 AM
To: dspace-tech@...
Subject: [Dspace-tech] Problem viewing PDFs with Firefox


Hi...

I can't recall if this has been mentioned on the list, but we (at
Cornell) have found a problem with our users viewing PDF's larger
that 6MB from DSpace if they are using Firefox.

For instance, the following item http://hdl.handle.net/1813/3900 has
a PDF that is 6.4MB.  If you try to view it with IE, it's fine.  If
you try to view it with Firefox, you get the message: "The file is
damaged and could not be repaired".  I am not sure where the
breakpoint is, but I know that other PDFs less than 6MB can be viewed.

***************************
George Kozak
Coordinator
Web Development and Management
Digital Media Group
501 Olin Library
Cornell University
607-255-8924
***************************
gsk5@...


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@...
https://lists.sourceforge.net/lists/listinfo/dspace-tech


-----Original Message-----
From: Shane Beers [mailto:sbeers@...] 
Sent: Thursday, January 29, 2009 2:48 PM
To: dspace-tech Tech
Subject: [Dspace-tech] Bug (?) opening a PDF in IR via firefox

I'm going to guess this is related to the default functionality of how  
firefox opens PDFs, but I'll ask here anyway. The collection admin for  
a particular section of our IR wrote me saying that she was getting an  
error opening a PDF from the IR. She would get the error "The file is  
damaged and could not be repaired" from Adobe Acrobat. If she right  
clicked and saved as... to her computer and opened it it was fine. It  
also opened fine from IE. My guess is that Acrobat is trying to open  
the file before it has actually completed downloading. The file is  
27mb, so that could potentially be the issue.

It works fine from my mac and firefox browser, however.

Is this a problem anyone else has run into? If so, is it something  
that can be "fixed" from DSpace's end?

Thanks.


Shane Beers
Digital Repository Services Librarian
George Mason University
sbeers@...
http://mars.gmu.edu
703-993-3742




--------------------------------------------------------------------------
----
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
DSpace-tech@...
https://lists.sourceforge.net/lists/listinfo/dspace-tech

This is a long existing issue with Firefox to handle big PDF. Probably
should report to Firefox. I do not know if others know how to deal with
this. 

You can use IE and Safari to open these PDFs. 

-----Original Message-----
From: Shane Beers [mailto:sbeers@...] 
Sent: Thursday, January 29, 2009 12:48 PM
To: dspace-tech Tech
Subject: [Dspace-tech] Bug (?) opening a PDF in IR via firefox

I'm going to guess this is related to the default functionality of how  
firefox opens PDFs, but I'll ask here anyway. The collection admin for  
a particular section of our IR wrote me saying that she was getting an  
error opening a PDF from the IR. She would get the error "The file is  
damaged and could not be repaired" from Adobe Acrobat. If she right  
clicked and saved as... to her computer and opened it it was fine. It  
also opened fine from IE. My guess is that Acrobat is trying to open  
the file before it has actually completed downloading. The file is  
27mb, so that could potentially be the issue.

It works fine from my mac and firefox browser, however.

Is this a problem anyone else has run into? If so, is it something  
that can be "fixed" from DSpace's end?

Thanks.


Shane Beers
Digital Repository Services Librarian
George Mason University
sbeers@...
http://mars.gmu.edu
703-993-3742




------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
DSpace-tech@...
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Yes, likewise, we placed a fix into the dspace 1.5 codebase that  
resolves this issue by setting a content-disposition threshold, there  
is a dspace.cfg property that can be set to control the threshold that  
the content disposition is set on a bitstream of a specific size.   
This is used to circumvent this browser issue.

Cheers,
Mark

On Jan 29, 2009, at 12:07 PM, George Kozak wrote:

> Shane:
>
> Yes, we encountered this problem as well with Firefox. Terry Reese  
> from Oregon State told me that there was a patch posted sometime ago  
> that forces the browser to initiate a download by setting the  
> Content-Disposition header element rather than inline viewing if the  
> file is over a specific file size.  The patch is found here:
> https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group_id=19984
>
> The patch sets the threshold to 20 MB.  I set our threshold to 5MB.
>
> At 02:47 PM 1/29/2009, Shane Beers wrote:
>> I'm going to guess this is related to the default functionality of  
>> how
>> firefox opens PDFs, but I'll ask here anyway. The collection admin  
>> for
>> a particular section of our IR wrote me saying that she was getting  
>> an
>> error opening a PDF from the IR. She would get the error "The file is
>> damaged and could not be repaired" from Adobe Acrobat. If she right
>> clicked and saved as... to her computer and opened it it was fine. It
>> also opened fine from IE. My guess is that Acrobat is trying to open
>> the file before it has actually completed downloading. The file is
>> 27mb, so that could potentially be the issue.
>>
>> It works fine from my mac and firefox browser, however.
>>
>> Is this a problem anyone else has run into? If so, is it something
>> that can be "fixed" from DSpace's end?
>>
>> Thanks.
>>
>>
>> Shane Beers
>> Digital Repository Services Librarian
>> George Mason University
>> sbeers@...
>> http://mars.gmu.edu
>> 703-993-3742

~~~~~~~~~~~~~
Mark R. Diggory
http://purl.org/net/mdiggory/homepage

On Mon, Feb 2, 2009 at 5:51 AM, Diggory Mark <mdiggory@...> wrote:

> Yes, we encountered this problem as well with Firefox. Terry Reese from
> Oregon State told me that there was a patch posted sometime ago that forces
> the browser to initiate a download by setting the Content-Disposition header
> element rather than inline viewing if the file is over a specific file
> size.  The patch is found here:
> https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group_id=19984
>
> The patch sets the threshold to 20 MB.  I set our threshold to 5MB.
>
>
I am very keen to see this fix make its way back into the official DSpace
source. And I too think that a 5 MB threshold is much more realistic.
-- 
Regards,

Andrew M.
http://www.andrewpetermarlow.co.uk

Hi ,

this patch has been committed to the codebase for the 1.5 release see
[dspace-src]/dspace/CHANGES or
https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group_id=19984
the tracker which has been set to closed, acceptes.

Claudia Jürgen




Andrew Marlow schrieb:
> On Mon, Feb 2, 2009 at 5:51 AM, Diggory Mark <mdiggory@...> wrote:
> 
>> Yes, we encountered this problem as well with Firefox. Terry Reese from
>> Oregon State told me that there was a patch posted sometime ago that forces
>> the browser to initiate a download by setting the Content-Disposition header
>> element rather than inline viewing if the file is over a specific file
>> size.  The patch is found here:
>> https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group_id=19984
>>
>> The patch sets the threshold to 20 MB.  I set our threshold to 5MB.
>>
>>
> I am very keen to see this fix make its way back into the official DSpace
> source. And I too think that a 5 MB threshold is much more realistic.
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech

Correct, and the threshold can be adjusted in one configuration to  
lower it to 5Mb, if seen fit we can adjust that in the default  
dspace.cfg for the next release.

Mark

On Feb 2, 2009, at 4:37 AM, Claudia Jürgen wrote:

> Hi ,
>
> this patch has been committed to the codebase for the 1.5 release see
> [dspace-src]/dspace/CHANGES or
> https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group_id=19984
> the tracker which has been set to closed, acceptes.
>
> Claudia Jürgen
>
>
>
>
> Andrew Marlow schrieb:
>> On Mon, Feb 2, 2009 at 5:51 AM, Diggory Mark <mdiggory@...>  
>> wrote:
>>
>>> Yes, we encountered this problem as well with Firefox. Terry Reese  
>>> from
>>> Oregon State told me that there was a patch posted sometime ago  
>>> that forces
>>> the browser to initiate a download by setting the Content- 
>>> Disposition header
>>> element rather than inline viewing if the file is over a specific  
>>> file
>>> size.  The patch is found here:
>>> https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group_id=19984
>>>
>>> The patch sets the threshold to 20 MB.  I set our threshold to 5MB.
>>>
>>>
>> I am very keen to see this fix make its way back into the official  
>> DSpace
>> source. And I too think that a 5 MB threshold is much more realistic.
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> DSpace-tech mailing list
>> DSpace-tech@...
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech

~~~~~~~~~~~~~
Mark R. Diggory
http://purl.org/net/mdiggory/homepage