This bug is related to 53363. Please read that first. There is an undocumented feature of the old NS API that Acrobat relies on in order to make byte range requests work. I am pretty sure I wrote a bug about this early this year, but my hard disk crashed so I can't easily produce the bug number. Basically, the behavior of Nav 4.X and earlier (and now Mac IE 5) is that when Nav encounters a PDF file, it starts an initial connection and pours the file into Acrobat (NPP_Write). It keeps that initial connection open and pouring **until* the first NPN_RequestRead. At that point, it kills the initial connection. NPN_RequestRead currently is broken (53363), so I am not sure if this undocumented feature is currently supported or not. I suspect not. And like the other aspects of byte range requests that I discuss in bugs 53363 and 53344, this feature is absolutely necessary to make mozilla a useable platform for Acrobat.

*** Bug 53369 has been marked as a duplicate of this bug. ***

*** Bug 53370 has been marked as a duplicate of this bug. ***

*** Bug 53373 has been marked as a duplicate of this bug. ***

*** Bug 53368 has been marked as a duplicate of this bug. ***

Was bug 35682 the one you were looking for?

setting bug status to new

Nominating as a high-priority bug for nsbeta1. This is one of the bugs in plug- in API backward compatibility of most concern to Adobe.

Moving to m0.9

av, this one depends on 53363 -- do you think that fix will kill this one? if so i won't track this one with the META bug.

Updating the URL field.

-->0.9.1

I don't see this geting fxied by 0.9.1 moving to 0.9.2.

Doug, did your NPN_RequestRead patch fix this too? If so, can you mark FIXED?

yup. this I fixed too.

rubberstamp-verified.

I thought only Redmond slapped a "Feature" label on something rather than reparing the bug, then called it "fixed"