B
Brandon
Running IIS 6, Classic ASP
Browser: IE and/or Mozilla
I have an application that allows users to store documents on my server.
When they need to access/download the documents, my application copies their
document to a staging directory (because they're renamed to a unique filename
for storage), then Respons.redirect()'ed to the staged file for download.
This works great for most files(.doc,.xls,.psd,.pdf). However, I have
discovered that for certain filetypes (.asp, .exe, .xfdl), the user gets a
message box with the message "Internet Explorer cannot download myfile.xfdl
from www.mysite.com. Internet Explorer was unable to open this Internet
site. The requested site is either unavailable or cannot be found. Please
try again later."
I have looked on the server, and the file is actually there. IIS just will
not let the user access/download it.
Mozilla downloads an htm page with a "page cannot be found" error.
Any thoughts? I have the directory established as its own application and
set not to execute anything -- so it shouldn't be confusing it with a
script/app.
Thank you all,
Brandon
Browser: IE and/or Mozilla
I have an application that allows users to store documents on my server.
When they need to access/download the documents, my application copies their
document to a staging directory (because they're renamed to a unique filename
for storage), then Respons.redirect()'ed to the staged file for download.
This works great for most files(.doc,.xls,.psd,.pdf). However, I have
discovered that for certain filetypes (.asp, .exe, .xfdl), the user gets a
message box with the message "Internet Explorer cannot download myfile.xfdl
from www.mysite.com. Internet Explorer was unable to open this Internet
site. The requested site is either unavailable or cannot be found. Please
try again later."
I have looked on the server, and the file is actually there. IIS just will
not let the user access/download it.
Mozilla downloads an htm page with a "page cannot be found" error.
Any thoughts? I have the directory established as its own application and
set not to execute anything -- so it shouldn't be confusing it with a
script/app.
Thank you all,
Brandon