Question

I have an IIS6 running on Windows Server 2003 (x86) and have written a custom handler (Not a handler for 404 errors).

When I try to access the handler by opening in a browser http://localhost/Priority1.Sync/Transfer.p1s, I get error 404 (404 0 in log file). Other pages in the web application work, e.g. http://localhost/priority1.sync/syncservice.asmx

The handler works fine on my IIS7 dev machine.

web.config is setup as follows:

<httpHandlers>
            <remove verb="*" path="*.asmx"/>
            <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
            <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
            <add verb="GET,HEAD" path="ScriptResource.axd" validate="false" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
            <add verb="*" path="*.p1s" type="MCS.Priority1.Sync.WebServices.TransferHandler, SyncService" />
</httpHandlers>

I have set an application extension for “*.p1s” (Default Web Site>Properties>Home Directory>Configuration>Mappings>Add).

Am I missing something else?

Thanks,
Andy

Answer 1

Do you have the “Verify that file exists” option in your custom handler IIS configuration checked or not?

IIS6 expects a physical file to exist by default. If there isn’t one, it won’t pass the request on to your handler at all. You need to disable this check, so it will send the request to your handler as expected.