Delivering with Apache is fine until you need to restrict access using Cocoon based user controls.
To summarize my understanding of the issues with PDFs...
* If your end users don't use any PDF plugin then everything will work fine.
* Certain Adobe PDF plugins combined with certain browsers require a correct file size to be returned in order for download to work. There are a lot of people out there with IE, PDF Plugin combinations that experience this issue - so it is a *real* issue if it doesn't work.
Here is the closed bug which covered this last time:
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7156>
Stuart.
On Thursday, December 5, 2002, at 01:00 am, Joerg Heinicke wrote:
Public Key - 1024D/88DD65AF 2001-11-23 Stuart Roebuck (Adolos)The people, who tested it, said, that it was not the IE problem, but browser independent. And the download in the different browsers gave different file sizes at the end.We have the same problem with Cocoon 2.0.1. Do you have a current version? First tests with 2.0.3 were okay, even if the code, you mention, has not changed. But maybe the tests only were okay by accident?
Maybe. AFAIK the dependency on the correct content length for displaying PDF is a IEx specific problem, other browsers may work without it.
We deliver the PDFs now simply via Apache, no Cocoon.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Key fingerprint = 89D9 E405 F8B1 9B22 0FA2 F2C1 9E57 5AB1 88DD 65AF
------------------------------------------------------------------------ -
Stuart Roebuck [EMAIL PROTECTED]
Systems Architect Java, XML, MacOS X, XP, etc.
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
