Files won't download

[Kavius]

I have a website I have migrated from ASP to ASP.NET. One of the things the site does is allow people to download files if they have appropriate permissions. In the old site when a user clicks on a file, the server copies it to a temporary folder, points IE at it, IE downloads the file, stores it in a temporary folder, and opens it with the appropriate viewer (IE, Adobe Reader, MS Word, couple of proprietary viewers). Everything is good.

With the new ASP.NET site, we go through the exact same procedure (copy/redirect) and Internet Explorer downloads the file, but does not appear to copy it to the temporary folder. When it goes to open the viewer, the viewer complains that it can't find the file.

A couple of tests later, it works with any browser except Internet Explorer. I have tested it with Firefox and Opera, and both work. IE works, as long as I have it passing through my proxy (so I can view the traffic for debugging). IE connected directly to the network fails.

Both the old site and the new site are running on the same server. The only difference between the two sites (that I can see so far) is that the ASP site has not had any .NET configuration done to it (hasn't needed it).

Does anyone have any ideas?

While somewhat related to this problem, it really isn't the same thing: thread333-1109570. I include it because there are similar symptoms, but very different root methodology.

 

[ca8msm]

I think it's actually a problem with IE/Temporary files rather than an ASP.NET problem, although I could be wrong.

I've seen the problem before and if the user saves the file as opposed to opening it, it will then work once the open the file from their system. It also sometimes works if you clear out the user's temporary files folder.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[Kavius]

Originally that's what I thought, and I still think there is something to it. The only problem is that we haven't released the new .NET site, and are still running the old ASP site. Users *can* download from the ASP site, but not the .NET site.

Now that I write that, this sounds more like an IIS configuration problem (can't think of what it would be though). There has to be something different between the configuration of the two sites on the server end, otherwise I would expect them to behave the same.