J
John Laco
Dear Gentlemen (and Ladies of course),
I am facing an interesting problem (which may be not be a problem). I
am running win2000 server IIS5 (with newest SP). This is our
development server and I am making an ACCESS-driven ASP applications.
For easy development purposes I have enabled the "Allow Directory
Browsing" in IIS in the "home" virtual folder, just to see whether
files are written by the ASP script in that folder. What I noticed is
when I try to simply download the files (ASP, TXT, HTM) by using the
Right-click "Save Target As…" using Internet Explorer (v 5.0)
the ISS tries to execute the files and always sends back the response
(file) in html type of format.
Thus, the files that are saved locally on my PC are always in HTML
format, also for the TXT files, which is quite strange. I have checked
the MIME types headers in IIS and everything seems normal. The TXT and
HTM extensions are not mapped to the ASP DLL engine.
Any ideas what can trigger this IIS behavior. This can be a good
mechanism for protecting the files to be viewed (downloaded) in
Browser (even TXT files!!!).
Greetings,
John.
I am facing an interesting problem (which may be not be a problem). I
am running win2000 server IIS5 (with newest SP). This is our
development server and I am making an ACCESS-driven ASP applications.
For easy development purposes I have enabled the "Allow Directory
Browsing" in IIS in the "home" virtual folder, just to see whether
files are written by the ASP script in that folder. What I noticed is
when I try to simply download the files (ASP, TXT, HTM) by using the
Right-click "Save Target As…" using Internet Explorer (v 5.0)
the ISS tries to execute the files and always sends back the response
(file) in html type of format.
Thus, the files that are saved locally on my PC are always in HTML
format, also for the TXT files, which is quite strange. I have checked
the MIME types headers in IIS and everything seems normal. The TXT and
HTM extensions are not mapped to the ASP DLL engine.
Any ideas what can trigger this IIS behavior. This can be a good
mechanism for protecting the files to be viewed (downloaded) in
Browser (even TXT files!!!).
Greetings,
John.