I'd like to be able to have all 404's redirect to the homepage of my site...
However, it's seems that perhaps by design this isn't allowed...
Using the umbracoSetting.config and setting <error404>HOMEPAGE ID</error404> results, I think, in iis catching the 404 and displaying the standard ASP.Net 404 page...
if I set the error404 id to be any other page on my site then it functions as required, redirecting the user to that node.
I can think of a few workarounds... (have a actual 404 page that does a second redirect, have an isapirewrite rule etc) but wondered if anyone could explain why the inbuilt handle 404 functionality won't all redirect to the homepage. (the root node of content in my case)
The only pages that work with the error404 seem to be ones where I have functionality for them to redirect to their first child node... If I remove this then all id's set in the error404 give the standard 404 message..
Guess I need to set up a clean installation and see if it works out of the box...
I can confirm... windows 2008 server, iis7.0.6000.16386 integrated pipeline .net4 with a new install with the simple start kit, the handle404 doesn't work out of the box.
If I change the site to run in classic, rather than integrated then *.aspx requests that don't exist get rewritten to the homepage, not redirected. (but only the aspx pages)
been through all the other posts and tried all sorts of things today... even tried to sift through failedrequest handlers in iis logs... and can't see anything the matter.
Next step I guess is to remove the inbuilt 404 handler and add my own to do exactly the same thing...
Umbraco 4.7.1.453 and handle404
I'd like to be able to have all 404's redirect to the homepage of my site...
However, it's seems that perhaps by design this isn't allowed...
Using the umbracoSetting.config and setting <error404>HOMEPAGE ID</error404> results, I think, in iis catching the 404 and displaying the standard ASP.Net 404 page...
if I set the error404 id to be any other page on my site then it functions as required, redirecting the user to that node.
I can think of a few workarounds... (have a actual 404 page that does a second redirect, have an isapirewrite rule etc) but wondered if anyone could explain why the inbuilt handle 404 functionality won't all redirect to the homepage. (the root node of content in my case)
In fact that's not my issue at all...
The only pages that work with the error404 seem to be ones where I have functionality for them to redirect to their first child node... If I remove this then all id's set in the error404 give the standard 404 message..
Guess I need to set up a clean installation and see if it works out of the box...
I can confirm... windows 2008 server, iis7.0.6000.16386 integrated pipeline .net4 with a new install with the simple start kit, the handle404 doesn't work out of the box.
you get the
Server Error
If I change the site to run in classic, rather than integrated then *.aspx requests that don't exist get rewritten to the homepage, not redirected. (but only the aspx pages)
been through all the other posts and tried all sorts of things today... even tried to sift through failedrequest handlers in iis logs... and can't see anything the matter.
Next step I guess is to remove the inbuilt 404 handler and add my own to do exactly the same thing...
Unless anyone out there can help?????
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.