You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Torsten Curdt <tc...@dff.st> on 2001/01/15 17:22:20 UTC
IE bug whith FOP-produced PDFs - again -sigh-
> > The Content-Disposition header is used to suggest a more appropriate
> > filename to the browser than the filename part of the request address
> > (see RFC 2616, section 19.5.1).
>
> > + response.addHeader("Content-Disposition", "attachment;
> > filename=bar.pdf");
>
> I suggest to use response.setHeader instead, because addHeader doesn't
> exist in JSDK2.1 or below and thus won't run with JServ.
...I thought we got it working. But #&* IE gives nothing but a blank
screen until we hit the reload button.
We tried:
1. order.xml?.pdf&media=pdf
-> blank screen
2. order.xml?media=pdf with
add/setHeader("Content-Disposition", "attachment;filename=order.pdf");
-> two popups for open/save
and also
add/setHeader("Content-Disposition", "inline;filename=order.pdf");
-> blank screen
3. We even mapped *.pdf to C1 and got
order.pdf?media=pdf
-> blank screen
(media=pdf creates the stylesheet PI as you might have assumed)
We're loosing all our hair.. ;)
I know this is a never ending thread...
..did we miss something?
--
Torsten
RE: IE bug whith FOP-produced PDFs - again -sigh-
Posted by Torsten Curdt <tc...@dff.st>.
Thanks for your efforts man! You are absolutely right!
We tried it with all our IE versions (5-5.5 with/without
ServicePack). Always the same behavior.
Now what.. put white text in background to make it bigger?! ;)
(Maybe we are lucky and the final content is enough)
Would be interesting at which size it wraps to working.
I remember the initial problem was the undefined
Content-Length, right?!
--
Torsten
> -----Original Message-----
> From: Peter Jacobs [mailto:peter.jacobs@advalvas.be]
> Sent: Tuesday, January 16, 2001 11:34 AM
> To: cocoon-users@xml.apache.org
> Subject: RE: IE bug whith FOP-produced PDFs - again -sigh-
>
>
> My suggestion probably didn't work for you, so I checked it again.
> Indeed, with some files I get the same symptoms: no display first
> time, but
> OK after a refresh.
>
> After some experimenting, it seems to be a problem with the size of the
> resulting PDF:
> a small PDF does not work, a bigger PDF does.
>
> you can see an example at:
> http://www.mediamagie.com/cocoondemo/foptest/fixIE/test.htm
>
>
> HTH,
> Peter Jacobs
RE: IE bug whith FOP-produced PDFs - again -sigh-
Posted by Peter Jacobs <pe...@advalvas.be>.
My suggestion probably didn't work for you, so I checked it again.
Indeed, with some files I get the same symptoms: no display first time, but
OK after a refresh.
After some experimenting, it seems to be a problem with the size of the
resulting PDF:
a small PDF does not work, a bigger PDF does.
you can see an example at:
http://www.mediamagie.com/cocoondemo/foptest/fixIE/test.htm
HTH,
Peter Jacobs
-----Original Message-----
From: Peter Jacobs [mailto:peter.jacobs@advalvas.be]
Sent: maandag 15 januari 2001 17:47
To: cocoon-users@xml.apache.org
Subject: RE: IE bug whith FOP-produced PDFs - again -sigh-
maybe this works:
order.xml?media=pdf&fixIE=.pdf
HTH,
Peter Jacobs
-----Original Message-----
From: Torsten Curdt [mailto:tcurdt@dff.st]
Sent: maandag 15 januari 2001 17:22
To: cocoon-users@xml.apache.org
Subject: IE bug whith FOP-produced PDFs - again -sigh-
> > The Content-Disposition header is used to suggest a more appropriate
> > filename to the browser than the filename part of the request address
> > (see RFC 2616, section 19.5.1).
>
> > + response.addHeader("Content-Disposition", "attachment;
> > filename=bar.pdf");
>
> I suggest to use response.setHeader instead, because addHeader doesn't
> exist in JSDK2.1 or below and thus won't run with JServ.
...I thought we got it working. But #&* IE gives nothing but a blank
screen until we hit the reload button.
We tried:
1. order.xml?.pdf&media=pdf
-> blank screen
2. order.xml?media=pdf with
add/setHeader("Content-Disposition", "attachment;filename=order.pdf");
-> two popups for open/save
and also
add/setHeader("Content-Disposition", "inline;filename=order.pdf");
-> blank screen
3. We even mapped *.pdf to C1 and got
order.pdf?media=pdf
-> blank screen
(media=pdf creates the stylesheet PI as you might have assumed)
We're loosing all our hair.. ;)
I know this is a never ending thread...
..did we miss something?
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
RE: IE bug whith FOP-produced PDFs - again -sigh-
Posted by Peter Jacobs <pe...@advalvas.be>.
maybe this works:
order.xml?media=pdf&fixIE=.pdf
HTH,
Peter Jacobs
-----Original Message-----
From: Torsten Curdt [mailto:tcurdt@dff.st]
Sent: maandag 15 januari 2001 17:22
To: cocoon-users@xml.apache.org
Subject: IE bug whith FOP-produced PDFs - again -sigh-
> > The Content-Disposition header is used to suggest a more appropriate
> > filename to the browser than the filename part of the request address
> > (see RFC 2616, section 19.5.1).
>
> > + response.addHeader("Content-Disposition", "attachment;
> > filename=bar.pdf");
>
> I suggest to use response.setHeader instead, because addHeader doesn't
> exist in JSDK2.1 or below and thus won't run with JServ.
...I thought we got it working. But #&* IE gives nothing but a blank
screen until we hit the reload button.
We tried:
1. order.xml?.pdf&media=pdf
-> blank screen
2. order.xml?media=pdf with
add/setHeader("Content-Disposition", "attachment;filename=order.pdf");
-> two popups for open/save
and also
add/setHeader("Content-Disposition", "inline;filename=order.pdf");
-> blank screen
3. We even mapped *.pdf to C1 and got
order.pdf?media=pdf
-> blank screen
(media=pdf creates the stylesheet PI as you might have assumed)
We're loosing all our hair.. ;)
I know this is a never ending thread...
..did we miss something?
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org