I have an application that allows one of our employees to manage a static web site. The data is stored in a database and he can change it as he wishes. When he saves the changes, it also scrapes the .aspx page that renders each page on the entire site, and writes it as an actual *.htm file in another folder. This allows the website to be deployed without relying on the server using the .NET framework.
To allow the links within the web pages to be accurate (i.e. direct to an .htm file), I have an HttpHandler in the web.config file that sends the request to an HttpModule class that I created. It checks to see if there is an actual .htm file in the edit application directory. If there is no .htm file, it is content-managed and resides in the database. If there is, it renders the actual file.
This works on my local machine running WinXP Pro, but not on our Windows 2000 Server test/development server. All settings seem to be the same. When I try to request a virtual .htm page on the development server, I receive the IIS 404 page... all black and white, not the .NET 404 page. This leads me to believe that it is never firing the HttpHandler, and IIS is rejecting it because there is no file at that location.
I do not have to use IIS application mappings on my local machine to get it to work, and everything seems to be the same in IIS. What could cause IIS to skip the HttpHandler section of the web.config file and to try to render the page itself?
To allow the links within the web pages to be accurate (i.e. direct to an .htm file), I have an HttpHandler in the web.config file that sends the request to an HttpModule class that I created. It checks to see if there is an actual .htm file in the edit application directory. If there is no .htm file, it is content-managed and resides in the database. If there is, it renders the actual file.
This works on my local machine running WinXP Pro, but not on our Windows 2000 Server test/development server. All settings seem to be the same. When I try to request a virtual .htm page on the development server, I receive the IIS 404 page... all black and white, not the .NET 404 page. This leads me to believe that it is never firing the HttpHandler, and IIS is rejecting it because there is no file at that location.
I do not have to use IIS application mappings on my local machine to get it to work, and everything seems to be the same in IIS. What could cause IIS to skip the HttpHandler section of the web.config file and to try to render the page itself?