How is the PDF being served to the user? Is it coming
from an ASP page and being Response.BinaryWrite'ed? The best work around
that I'm using for this problem is this:
I persist the file on the server, then send this to the
browser:
<html><head>
<script language="javascript">
<!--
window.location.href='<%=path%>'
//-->
</script>
</head><body></body></html>
This way, IE will go fetch the file itself. If you are
using IIS, save the docs in their own folder, then go into the IIS setting, and
enable content expiration (it's on the HTTP Headers tab) just for that folder
and set it to expire immediately. If you don't do this, IE will keep
pulling the PDF from it's cache if you re-use filenames.
:)
--
Diversa ab illis virtute valemus.
|
- Acrobat 5.0 Error Rachael Blank
- RE: Acrobat 5.0 Error David B. Bitton
- RE: Acrobat 5.0 Error Rachael Blank
- Re: Acrobat 5.0 Error David B. Bitton
- Re: Acrobat 5.0 Error Matt Savino