Hello (especially Ulrich...).
I've took a close look at the Problem with wrong displayed PDFs in IE
5.x. generatet by Coccon-FOP. I had no explanation why it did not work
generatet from cocoon directly, but worked perfectly when the same
stream saved as a file was served from the file system.
I've analysed the returend header with telnet and found the following
difference:
A) From Cocoon:
HTTP/1.0 200 OK
Content-Type: application/pdf
Servlet-Engine: Tomcat Web Server/3.2.2 (JSP 1.1; Servlet 2.2; Java
1.3.1; Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.)
%PDF-1.3
...
B) From Filesystem (same stream saved as file)
HTTP/1.0 200 OK
Content-Type: application/pdf
Content-Length: 980
Last-Modified: Wed, 04 Jul 2001 16:37:43 GMT
Servlet-Engine: Tomcat Web Server/3.2.2 (JSP 1.1; Servlet 2.2; Java
1.3.1; Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.)
%PDF-1.3
...
Note the difference, that the Content-Length is only specifed when
served from filesystem.
As a primitive Test i added the following Header in my XSP page:
<xsp:logic>
response.addHeader("Content-Length", "980");
</xsp:logic>
and the generated PDF is displayed correctly and perfect. Of course this
is no direct solution, because the size differs with each pdf. I testet
it with IE 5.00.3315.1000 and IE 5.50.4134.0600.
Unfortunately i've now idea where in cocoon it would be possible to set
the content length for an serializer within the complex framework all
around (the FOPSerializer handles only a output stream).
>>> Has anyone an idea? Any statement from FOPSerializer-Developers?
Stefan
---------------------------------------------------------------------
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]>
