Hi All,

I was able to figure out the cause and find a solution for the PageNotFoundHandler not working on IIS 7. The problem also surfaced on this recent thread. Basically it turns out that this is an IIS 7 specific issue, it worked fine all along on IIS 6 and it works fine on my Win 7 development machine which has IIS 7.5. So until recently when I moved mojoportal.com and demo sites from IIS 6/Win 2003 to IIS7/Win 2008 I was not seeing this issue myself. I really had not noticed the 404 handler not working on this site and demo.mojoportal.com after the initial move until someone pointed it out.

So after some research I found there is a way to change this behavior on IIS 7 using some command line commands, however, I'm not command line guru and was hoping for some easy to change setting from the UI so I kept looking a bit and found this solution in Rick Strahl's blog which involves 1 line of code added to our PageNotFoundHttpModule:

app.Context.Response.TrySkipIisCustomErrors = true;

I did not have a test environment with IIS 7 all setup so I deployed a new build on demo.mojoportal.com to verify this solved the issue and then also redployed a new build here on mojoportal.com to solve it here.

This fix will be in svn trunk by later tonight and will be in the next release.

Best,

Joe

Hello All,

Okay, so I used this command to allow the PassThrough of the response from the PageNotFoundHandler:

C:\Windows\System32\inetsrv>appcmd.exe set config "websiteName/" -section:system.webServer/httpErrors -existingResponse:PassThrough

And it added this to my web.config after the handlers section in the system.webServer section:

<httpErrors existingResponse="PassThrough" />

So, I copied that line to another web.config on a different site and all is well with the PageNotFoundHandler.

HTH,
Joe D.

Okay, I have a new question about this, and I'm not sure if this is a bug or a feature request.

If you navigate to http://demo.mojoportal.com/bogus/default.aspx, you get the friendly 404 page.

However, if you navigate to http://demo.mojoportal.com/bogus, http://demo.mojoportal.com/bogus/, or http://demo.mojoportal.com/bogus/index.html, you receive the generic IIS 404 page.

Is it possible to make the URLs in the second scenario also bring up the friendly 404 page? This is very important to us since our current site is HTML based, and without this capability, when we cut the site over to mojoPortal, all existing bookmarks and previously published URLs will lead to a generic 404 page. Obviously, we'd much prefer to have the friendly 404 page come up instead.

Thanks as always, Joe!

Jamie

Hi Jamie,

Scratch that. I shoud've tested before posting, not afterwards. I have this setting on my website but the friendly 404 isn't showing up when I use something like /bogus. I thought it would.

I will keep trying. Maybe I'll figure it out.

Thanks,
Joe D.

Hey guys, thanks for the tips. I believe I have this figured out now, thanks to this page. For step 6, I used the option "Execute a URL on this site" and pointed it to /PageNotFound.aspx so mojoPortal would handle the error, and I wouldn't need to worry about custom styling a static page. Now, all 404 requests seem to be going to mojoPortal's friendly page. Yay! The change also correctly affects sub-sites.

As a result of this change, the following section was added to Web.config below the <handlers> section "Handlers for IIS 7.0 Integrated mode":

<httpErrors>
<remove statusCode="404" subStatusCode="-1" />
<error statusCode="404" prefixLanguageFilePath="" path="/PageNotFound.aspx" responseMode="ExecuteURL" />
</httpErrors>

Joe, can you include this section in the default Web.config you are distributing with mojoPortal? I think this would be a very worthwhile change, as long as it doesn't interfere with people using versions of IIS other than 7.

Jamie