Solution 1:
Open your Acrobat, find Options, find something about integration among
Acrobat and Browser
(like 'embed Acobat window in browser' or something like that) - and disable
it.
Result - IE senses PDF - passes it to Acrobat - Acrobat runs in a window,
separate from browser (IE) -
all works fine.
Yes, it requires users to alter their Acrobat options, that's unfortunate,
but it works.
Solution 2:
Generate PDF, save it in temmp PDF file,
redirect User's browser to this file (since content length is known - no
problems with IE),
delete temp file 1 minute later.
Solution 3:
Uli, humble yourself, the relaity is the Evil Empire wins the browser
battle.
----- Original Message -----
From: "Carsten Ziegeler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 05, 2001 7:41 AM
Subject: AW: [C2] Possible Solution for PDF Bug with IE 5.x !??
> > Torsten Curdt wrote:
> >
> > > > > And a second: I downloaded your example from ulim/iebug and
> > > experimented
> > > > > a bit with it. If i save the generatet pdf in a file and put it in
> > > the
> > > > > same directory and call it, it works in all browsers, including IE
> > > 5.5.
> > > > > How do you explan this? There should be no difference between the
> > > > > streams?
> > > >
> > > > As I said, IE does some checks on the stream, if it arrives via
HTTP,
> > > > which it doesn't do, when opening a file from the filesystem.
> > >
> > > No, you misunderstood me. I saved the PDF stream in a file, put it in
> > > the webapps/<Context>-directory and served it using tomcat via HTTP,
> > > same context and server as the cocoon output.
> > > Ever tried this? Try it with your bug sample, it takes just some
> > > seconds. How do you explain this difference?
> >
> > AFAI remember the thing that really solved the IE-PDF problems in C1
> > was setting the Content-Length header. This would fit in the
> > picture you described...
> > But this needs to be double-checked...
> >
> > But AFAI understood setting a Content-Length header in C2 could be a
> > problem because we have streams - no documents.
> >
> > So what about creating the cache object first and then serving the
> > request from cache - so we know about the size of the object.
> >
> > Maybe Carsten can tell if this possible at all?
> >
> As far as I remember there were some strange problems with pdf and
> content length. I am not quite sure anymore, perhaps the mail archives
> contain some old mails about this topic.
>
> I use the IE 5.5 and have no problems with PDF (Acrobat Reader 5).
>
> The content length is set when the response is served from the cache
> or when it is put into the cache.
> (As the acrobat reader plugin for the ie requests the pdf document
> twice the second request is served from the cache and has the
> content length set anyway).
> So if your response is cacheable, the content length is set. If your
> response is not cacheable there is currently no way to detect the
> length of the response, so the content length is not set.
>
> I know this doesn't help at all for this problem but perhaps
> there is something in the mail archive (which is currently down...)
>
> Carsten
>
> > --
> > Torsten
> >
> >
> > ---------------------------------------------------------------------
> > Please check that your question has not already been answered in the
> > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> >
> > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > For additional commands, e-mail: <[EMAIL PROTECTED]>
> >
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
