Posted on: 5/26/2011 1:08:55 AM | Views : 776

I have the following scenario :
My web app installed on Windows 7, and linking to it via a browser running on Windows 2008. I call an ASPX which uses the following code to initiate a file download :
HttpResponse response = HttpContext.Current.Response; response.ContentType = mimeType; response.AppendHeader("Content-disposition", "attachment; filename=" + fileName); response.WriteFile(absolutePath); response.End(); where:  mimeType is set depending on file type, fileName is file to be downloaded, absolutepath is shared folder + fileName on Windows 7 box
The application allows file transfers across nextworks and works fine without using SSL ( ie http), but as soon as I switch to SSL (https) I hit the following problem :
1)  The filename in the file download pop-up becomes corrupted with the url of the ASPX page,
...

Go to the complete details ...