I too was experiencing issues with blank screens and errors downloading the pdf from our secured website.
Found the following contents from a blog...
---Start of blog
I found this article and it started me down the right path, but was not the definitive answer, so I wanted to share my finding in hopes of helping others. After the fact I was able to recongnize that some of the above posters came to the same conclusions as me, but no one explicitly stated them.
My environment is SSL, PDF or RTF download, IE6+, my users where getting the “file could not be written to the cache” error.
This MS KB entry gives the details (and suggests horrible registry hacks)
http://support.microsoft.com/?kbid=323308 [^]
I choose a simpler route, I made sure my web application did not send any of the following:
Cache-control:no-store
Cache-control:no-cache
Pragma: no-cache
and then make my users have unchecked the “Do not save encrypted pages to disk” in “Internet Options / Advanced” (unchecked _is_ the default setting, but some users have changed it)
-- End of blog
I found that adding the registry hack worked for me. Even a workmate that that was getting a blank screen started working.
I've tested with both IE6 and IE7 with the same results. I would suspect the DrawToWeb method is sending the above cache controls to IE browsers.
Both my workmate and I have both .Net 1.1 and 2.0 installed. We are using generator 3.x.