🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.reader
Article #1033

Large PDF in Firefox: The file is damaged and could not be repaired.

#1033
From: Jan_Tosovsky
Date: Mon, 16 Feb 2009 15:36
9 lines
1487 bytes
Hello Everyone,

we have located several PDF files on local webserver. We access them via html page. With default Apache server settings the files are loaded on each back/forward button. I've found it is due to the splitting the file into smaller parts during download. If HTTP header in server setting is changed to "Header set Accept-Ranges none", files are loaded in one block and already loaded PDF file is then displayed immediately (without redownload) on back/forward buttons. But it has one strange side effect if PDF file is quite large (35MB in our case). While in MSIE everything still works fine, in Firefox we get the error message "The file is damaged and could not be repaired."

I've found the similar problem here:
Robert Lee Anderson, "The file is damaged and could not be repaired." #7, 29 Jul 2008 6:03 am </webx?14@@.59b5bb0c/6>
but it doesn't help.

Is there any limitation in Firefox plug-in?
Technical Details
Message-ID: <59b7f10f.-1@webcrossing.la2eafNXanI>
Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!newshub.sdsu.edu!webcrossing

Show Full Headers
Complete Article Headers
X-Google-Thread: 10273d,ae55627ac78c6dd5,start
X-Google-Attributes: gid10273d,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: Jan_Tosovsky@adobeforums.com
Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.reader
Subject: Large PDF in Firefox: The file is damaged and
 could not be repaired.
Message-ID: <59b7f10f.-1@webcrossing.la2eafNXanI>
Date: Mon, 16 Feb 2009 07:36:50 -0800
Lines: 19
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit