Page Not Found

Page Not Found

Page Not Found Overview

  • Occurs when an HTTP request does not correspond to a resource on the Web server
  • The Web server responds with the HTTP 404 Page Not Found status code and markup providing an error message known as the 404 page
  • If IIS cannot use ASP.NET to process a resource request, then it attempts to serve a file from disk
  • If the file does not exist, IIS activates the 404 page defined through the IIS management console

Sitecore Page Not Found Management

  • If a URL does not correspond to Sitecore content or a file on disk, then Sitecore activates the URL specified by the ItemNotFoundUrl value of /configuration/sitecore/settings/setting in web.config
  • If a Rich Text Editor (RTE) field contains a link to an item that does not exist, Sitecore renders that link as a link to the URL specified by the LinkItemNotFound value of /configuration/sitecore/settings/setting in web.config
  • For example pipeline processors that handle the HTTP 404 Page Not Found condition, see
  • <configuration>
    • <sitecore>
      • <settings>
        • <setting name="ItemNotFoundUrl" value="/sitecore/service/notfound.aspx" />
        • <setting name="LinkItemNotFoundUrl" value="/sitecore/service/notfound.aspx" />

The PageNotFound Module

  • A free shared-source module available at the Sitecore Marketplace
  • Adds a processor to the httpRequestBegin pipeline
  • Provides may functions to developers for managing HTTP 404s
    • Apply custom 404 pages for each web site in the Sitecore instance
    • Redirect to an alternate page
    • Redirect to a search page and pass the path in the failed URL as a search query
    • Log 404 requests and the referring page