I got the class snippet from a colleague, and it may require a bit of modifying to scale to other solutions.
I would still prefer to use umbracos native way, but I seem to always run into trouble when I try to implement it, probably due to settings in either the solution or in IIS.
The last response to this is long a go, but for every one how is using IIS 6 here is the server setting that solved the issue for me.
In web.config add the following line to <system.webServer> section:
<httpErrors existingResponse="PassThrough" />
Be sure <httpErrors> is not already defined, otherwise you get an error.
For IIS 7 or newer this setting is not necessary, but it will not break your solution when you move the application to such a machine, thus it is save to add the line.
I had a similar problem with a new website on Umbraco 7. The Prod-server was somehow configured to use IIS errors, so I found a solution by setting trySkipIisCustomErrors="true" web.config under web.routing
IIS 6 and 404 problem.
I usually run into problems integrating 404 pages in umbraco. And once more I can't seem to figure out what I'm doing wrong.
I have an umbraco 4.7 running on IIS 6.
I have inserted my 404 nodeId in the umbracoSettings.config like so:
But still I get the standard server error from IIS:
Server Error
Can anybody enlighten me on what I need to do?
I prefer to use umbracos built-in handling but I'm open to other suggestions though I have tried to implement my own custom handler.
Hope someone can help.
Best regards
- Sune
Hi. Is it really IIS 6? This standard error page looks more like IIS7. And also, do all other pages work ok?
Hi Fengelz
Have you recycled the app pool after setting up the id of the intended 404 page?
/Jan
@Rodion I'm pretty certain it is IIS6 (Thats what it told me under help->about in the IIS Manager)
@Jan I haven't tried that. I'll see if I get a chance to test it tomorrow.
Thanks for your replies
- Sune
Tried to recycle the app pool, unfortunately to no change.
I found a .NET solution to the current problem so I'm over the hump for now. Would be nice to know how to handle this problem in the future though :/
- Sune
Hi Fengelz
Do you mind sharing your solution? Others might benefit from your approach if they have the same issues as you did :)
/Jan
Sure. Heres a gist: https://gist.github.com/1336018
I got the class snippet from a colleague, and it may require a bit of modifying to scale to other solutions.
I would still prefer to use umbracos native way, but I seem to always run into trouble when I try to implement it, probably due to settings in either the solution or in IIS.
- Sune
Hi Sune
That's great :)
I also just came accross this entry on the wiki: http://our.umbraco.org/wiki/how-tos/how-to-implement-your-own-404-handler
/Jan
Yeah. I tried that as well, but couldn't get it working, which led me to the conclusion that it is some basic server setting that messes with me :).
But I'm working on another solution with the similar problem. I'll be sure to update this thread if I come across the solution.
- Sune
The last response to this is long a go, but for every one how is using IIS 6 here is the server setting that solved the issue for me.
In web.config add the following line to <system.webServer> section:
<httpErrors existingResponse="PassThrough" />
Be sure <httpErrors> is not already defined, otherwise you get an error.
For IIS 7 or newer this setting is not necessary, but it will not break your solution when you move the application to such a machine, thus it is save to add the line.
Yours
Dirk
I had a similar problem with a new website on Umbraco 7. The Prod-server was somehow configured to use IIS errors, so I found a solution by setting trySkipIisCustomErrors="true" web.config under web.routing
<web.routing
trySkipIisCustomErrors="true"
internalRedirectPreservesTemplate="false">
</web.routing>
Cheers,
Niels
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.