>> Well I was able to do a quick test using a default setup of Tomcat and  
>> the Acrobat plug-in loads the page just fine in IE/Win.  So it's  
>> definitely down to some setup in Jetty/Cocoon/Lenya that's causing the  
>> problem.  Gregor, how does one set these headers in the sitemap?  And  
>> do you mean the publication-sitemap.xmap in each pub or the overall  
>> sitemap?  Did you create a pipeline that made this work for all PDF  
>> files?:
>> 
> 
> <map:pipeline type="noncaching">
>    <map:parameter name="expires" value="access"/>
>    <map:match pattern="**/*.pdf">
>      ... stuff in here ...
>    </map:match>
> 
> should take care of the cache expiry headers

Well I added the following pipeline into my pub's sitemap file:

<map:pipeline type="noncaching">
  <map:parameter name="expires" value="access"/>
  <map:match pattern="**/*.pdf">
    <map:read src="resources/authoring/{1}/{2}.pdf" 
mime-type="application/pdf"/>
  </map:match>
</map:pipeline>

Then I go to Lenya, click on the link in IE/Win with Acrobat 7 combination and 
the file is working.  Thank God, I think to myself.  I finally solved the 
problem.  So then I check out the live environment - same computer, same setup. 
 "The file is corrupt or damaged and cannot be repaired."  So what the heck?  
It doesn't make any sense - it seems to be completely random.  I'm serving the 
same file on the same computer and same setup with the only difference is one 
is in the authoring environment and the other is in the live environment and 
the results are different.  Then some files now work in the live environment 
and others do not.

Just as an example, go ahead and check out this page: 
http://alumni.hiram.edu/events/homecoming.html. Click on the big link using 
IE/Win with Acrobat Reader as plugin and see what you get.  I continue to get 
file damaged errors, but some people say they can see it fine.  It just seems 
so random.  Anyone have any ideas?  I'm feeling pretty helpless on this one...

Jon

<<winmail.dat>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to