Hi to everyone!
We have an asp.net application (Framework 1.1) and we had to add the
functionality of rewriting urls, for this we used a wildcard application
mapping on our development machines (Windows XP Pro with IIS 5.0).
Everything worked fine.
Then we installed this application on a Windows Server 2003 with IIS 6.0.
When we added the wildcard application mapping (which it's a bit different
from IIS 5.0), pointing to the aspnet_isapi.dll, two things happened:
1) We saw thru the task manager that it consumed lots of CPU
2) We tried to access the site, and it seemed to be hung up, and it couldn't
handle files like css, js, etc, even when in our development machines
everything worked fine. The IIS logs didn't show any error.
We removed the mapping and at least we could access the site with its normal
look-and-feel.
Then we tried adding a .js mapping, just to see what happened, and again we
couldn't access the site. We remove it and everything worked again. The same
happened adding a .css mapping, etc.
Please, could anyone suggest what could be possibly going on (IIS, server
configuration, etc)?
Any help would be greatly appreciated! Thanks in advance!
Gaby