« Previous Next »

• 08-13-2008, 12:44 PM

  grennis1 Joined on 08-13-2008, 12:41 PM Posts 2

  Wilcard Application Mappings on IIS5.1 Reply Contact I am having a problem with wildcard application mappings on IIS5.1. I am trying to establish a wildcard so that aspnet_isapi will handle all requests. According to instructions I have found, I simply need to map ".*" to that DLL and I'm done. The problem is that when I do this, any file with an extension (i.e., "site.css") immediately returns error 404. Paths without extensions (i.e., "/products/browse") do indeed work by passing the request to aspnet_isapi. Note that I did get this work just fine on IIS6. My problem is IIS5.1's failure to handle files with an extension once I establish the wildcard map. Can anyone please advise? Thanks

• 08-13-2008, 3:44 PM

  In reply to

  jabailo Joined on 11-12-2007, 8:17 PM Posts 18

  Re: Wilcard Application Mappings on IIS5.1 Reply Contact  I just posted a similar query...however, I do not have an answer. I was able to get wildcards working for II6.0 for a virtual directory only. I could not get them to work for a web site (top level).   I did however test with a 5.0 server and also did not get it to work...I get the 404 error after adding the wildcard mapping for aspnet_isapi.dll.     John Bailo

• 08-13-2008, 6:48 PM

  In reply to

  grennis1 Joined on 08-13-2008, 12:41 PM Posts 2	Re: Wilcard Application Mappings on IIS5.1 Reply Contact Yeah it just seems to be completely broken out of the box. Not sure what's going on with this. I guess Microsoft has moved on and doesn't even spend a moment on support of IIS5 anymore.