Custom 404 works on local production web browser but not when called from a different machine
So this is a new one!
I have a custom implemented 404 Handler. The handler works fine in development. I promoted the site to production and the 404 works from the server when I am browsing on it, but when I call the site from my work station the 404 does not work.
Anyone ever seen this before? I have the same code implemented in a couple of my Umbraco 6 instances and it works flawlessly.
Sound like you need to check the <customErrors mode="On" /> node in web.config on the production server. It should probably bet set to "On" depending on how you've setup 404 handling.
All good advice, I'll give it a go. Also, I am seeing the IIS 404 and not the plain Umbraco 404. What puzzles me is that should fail ALL the time and not just when I am looking at it from a different machine.
Custom 404 works on local production web browser but not when called from a different machine
So this is a new one!
I have a custom implemented 404 Handler. The handler works fine in development. I promoted the site to production and the 404 works from the server when I am browsing on it, but when I call the site from my work station the 404 does not work.
Anyone ever seen this before? I have the same code implemented in a couple of my Umbraco 6 instances and it works flawlessly.
Thanks
Phillip
When you say doesn't work, what do you actually see?
The default Umbraco plain text 404 or the Server IIS 404?
Sound like you need to check the <customErrors mode="On" /> node in web.config on the production server. It should probably bet set to "On" depending on how you've setup 404 handling.
If you're seeing the default IIS Server 404 try adding
To your web.config as that's caught me out a few times
All good advice, I'll give it a go. Also, I am seeing the IIS 404 and not the plain Umbraco 404. What puzzles me is that should fail ALL the time and not just when I am looking at it from a different machine.
Well, that web.config entry did it. I knew that entry was missing, but because it was working locally on the server, it was throwing me off.
Thanks for the help!
is working on a reply...