Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Phillip Turner 98 posts 412 karma points
    Nov 11, 2015 @ 19:41
    Phillip Turner
    0

    Custom 404 works on local production web browser but not when called from a different machine

    Using Umbraco 7
    Umbraco 7

    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

    Copy Link
  • Matthieu Nelmes 102 posts 385 karma points
    Nov 11, 2015 @ 20:49
    Matthieu Nelmes
    0

    When you say doesn't work, what do you actually see?

    The default Umbraco plain text 404 or the Server IIS 404?

    Copy Link
  • ZNS 60 posts 198 karma points
    Nov 11, 2015 @ 22:13
    ZNS
    0

    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.

    Copy Link
  • Matthieu Nelmes 102 posts 385 karma points
    Nov 11, 2015 @ 22:22
    Matthieu Nelmes
    101

    If you're seeing the default IIS Server 404 try adding 

    <httpErrors existingResponse="PassThrough"/>

    To your web.config as that's caught me out a few times

    Copy Link
  • Phillip Turner 98 posts 412 karma points
    Nov 12, 2015 @ 02:52
    Phillip Turner
    0

    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.

    Copy Link
  • Phillip Turner 98 posts 412 karma points
    Nov 12, 2015 @ 13:32
    Phillip Turner
    1

    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!

    • Phillip
    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft