D
danielle.m.manning
I am using IIS 6.0 and plain old ASP. My IIS server is for
development, and is currently running different websites under
different virtual directories. Most of these websites use ASP.NET, but
we have a client on an old technology, and we wanted to put work for
them under the same website in a different virtual directory.
I set the virtual directory up successfully, and can access my site
via:
http://localhost/mynewclient/default.html
where default.html is just a "hello world" page. Comes up just fine.
The problem is, if I were to rename this page which contains html to a
..asp extension -- i get a 404 error. Is there something special I need
to do in IIS to allow the asp extensions to be run successfully?
Thanks for any insight,
Danielle
development, and is currently running different websites under
different virtual directories. Most of these websites use ASP.NET, but
we have a client on an old technology, and we wanted to put work for
them under the same website in a different virtual directory.
I set the virtual directory up successfully, and can access my site
via:
http://localhost/mynewclient/default.html
where default.html is just a "hello world" page. Comes up just fine.
The problem is, if I were to rename this page which contains html to a
..asp extension -- i get a 404 error. Is there something special I need
to do in IIS to allow the asp extensions to be run successfully?
Thanks for any insight,
Danielle