I have several links on a webpage. They are really quite ordinary and all of them have the following form: http://www.<server-name>.DocViewer.aspx?id=<number> This workswhen I use http but doesn't when I try to run on https. I did change http to https but that had no effect. Over https I keep getting a dialog that says: Internet Explorer cannot download DocViewer.aspx from <server-name>. Internet Explorer was not able to open this Internet site. The requested site is unavailable or cannot be found. Please try again later. Could there be some property that needs to be set? I am running ASP.NET 3.5 on IIS7. DocViewer.aspx ultimately opens attachments e.g. pdf files. Could it be that this is what is causing the problem? That there is no secure channel between the server and the viewer for the specific attachment? Thanks, Gautam Post Edited (gautams) : 11/12/2008 8:42:24 PM GMT
Again it turns out that self-help is the best help. The problem is with caching. It must be made sure that no-cache is not set for downloadsto work over https.
My appwas adding headers to every page so thatthe page woulda) expire immediately b) not be cached. That worked fine except for the file download page which stopped working in IE7 the moment SSL was enabled. Turning off the immediate expiry had no effect but when the no-cache header was removed, file downloads started working. Today I looked on microsoft.com and came up with this: http://support.microsoft.com/kb/323308 Interestingly, Chrome had no problems with either protocol.
