httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@znep.com>
Subject Re: [BUG]: "PDF served by 1.2bX can't be read by Netscape Win95 Acrobat Plugin" on Solaris 2.x (fwd)
Date Wed, 05 Feb 1997 23:43:15 GMT
See also PR#125 and PR#154.  

Someone with a Windows client should at least verify it, and see if it
sitll happens if you try turning off selected 1.2 features.

On Wed, 5 Feb 1997, Rob Hartill wrote:

> 
> ---------- Forwarded message ----------
> Date: Tue Feb 4 21:05:04 1997
> From: casey@princeton.edu
> To: apache-bugs%apache.org@organic.com
> Subject: [BUG]: "PDF served by 1.2bX can't be read by Netscape Win95 Acrobat Plugin"
on Solaris 2.x
> 
> Submitter: casey@princeton.edu
> Operating system: Solaris 2.x, version: 
> Version of Apache Used: 1.2b6
> Extra Modules used: 
> URL exhibiting problem: 
> 
> Symptoms:
> --
> 
> Just sending this along in case you hadn't seen
> the flurry of discussion about this problem in
> the comp.text.pdf and comp.infosystems.www.servers.unix
> newsgroups.  Here is a good description of the
> problem from a newsgroup post.  I am seeing the
> exact same behavior...
> 
> From: jrmase@paisano.com (Rusty Mase)
> Newsgroups: comp.text.pdf
> Subject: http 1.1 and PDF
> Date: Thu, 30 Jan 1997 18:07:37 GMT
> Organization: Environmental Technical Services Co.
> Lines: 42
> Message-ID: <32f0d4ff.11972143@news2.bga.com>
> Reply-To: jrmase@paisano.com
> NNTP-Posting-Host: apm0-55.realtime.net
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> X-RTcode: ef3c094e32bd28a89bf0e397
> X-Newsreader: Forte Agent .99f/32.299
> 
> My ISP just upgraded to  Apache 1.2b1 which has disabled my ability to
> download the larger PDF documents from my site using Win 95/Netscape
> 3.0 with Adobe Reader plug-in.  The files appear to download properly
> but the Adobe Reader stays minimized on the toolbar and does not open
> the file.  Additionally, a pdf file is not placed in cache.  Other
> operating systems seem to work okay and I can successfully "save link
> as" under Netscape set-up.  Smaller files 15 Kb or so also work fine
> using the plug-in.
> 
> The problem may be related to the new 206 Partial Content Status Code
> in http 1.1 as the file tries to download to Netscape using both 200
> and 206 sequentially and the combination of the two does not download
> a reviewable file.
> 
> My access logs review the following sequence of events:
> 
> "GET /pdf/13de96e.pdf HTTP/1.0" 200 24576
> "GET /pdf/13de96e.pdf HTTP/1.0" 206 327875
> 
> while my error log has the following entry timed with the first access
> line:            send lost connection to client
> 
> My question is does Netscape or Adobe Reader originate the 206
> "partial GET request" and my server does not know how to handle it?
> 
> Is there any relations between the 206 "partial GET request" and
> optimized PDF documents (my files are not optimized).
> 
> Or, does my ISP merely have his new configurations set wrong and I
> will just have to wait until they get it right?
> 
> Apologies in advance for the topic here but I know of no better forum.
> 
> Rusty Mase   jrmase@paisano.com
> http://www.wetlands.com/regs/tlpge04b.htm
> 
> --
> 
> Backtrace:
> --
> 
> --
> 
> 


Mime
View raw message