ASP.NET Pipeline settings blocking Web Service Calls RRS feed

  • Question

  • User47597812 posted

    I'm working on a large ASP.NET application in the middle of it's life cycle. The application is mapping wildcards (all extensions) to the ISAPI dll (configured in IIS). The result is that an HTTP handler runs and redirects to valid pages.

    Because of this configuration, I am unable to access any .asmx (Web Services). I am getting a "404 The Resource could not be found". My theory is that the wildcard extension mapping is blocking my web service call from being piped correctly.

    For example a web service like ' http:\\localhost\MyApp\MyWebService.asmx\MyFunction1 ' is not being handled by IIS as a web service but rather like I described above. The web service method name is throwing it off because IIS thinks it's a file with no extension and pipes it through as such (instead of as web service).


    Thank you very much for your help.

    Monday, February 9, 2009 9:43 PM