Sitecore keep or preserve url when 404 page not found

In some cases we don't want to redirect the users to a 404 page only because the users typed in the url wrongly. In this case what we want is to show the 404 content but keep or preserve the url. This way they can correct the url without having to type it in from scratch.

The way to do this in Sitecore is to execute some code before the OOTB RedirectOnItemNotFound code.

Create a config patch:

?
1
2
3
4
5
6
7
8
9
<sitecore>
  <pipelines>
    <httpRequestBegin>
  <!-- Overrides the default RedirectOnItemNotFound method to better handle 404 return codes. Run it before the standard Sitecore.Pipelines.HttpRequest.ExecuteRequest -->
  <processor patch:before="processor[@type='<namespace>.ExecuteRequest, Sitecore.Kernel']" type="<namespace>.ExecuteRequest, <assembly>"/>
  </processor>
    </httpRequestBegin>
  </pipelines>
</sitecore>

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
public class ExecuteRequest : Sitecore.Pipelines.HttpRequest.ExecuteRequest
{
    protected override void RedirectOnItemNotFound(string url)
    {
        var context = HttpContext.Current;
 
        try
        {
            Log.Info(string.Format("Url: {0}", url), this);
 
            string content;
            using (var webClient = new WebClient())
            {
                webClient.Headers[HttpRequestHeader.UserAgent] = "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)";
                content = webClient.DownloadString(string.Concat(domain, url));
            }
 
            // Send the NotFound page content to the client with a 404 status code
            context.Response.TrySkipIisCustomErrors = true;
            context.Response.StatusCode = 404;
            context.Response.Write(content);
        }
        catch (WebException ex)
        {
            WebResponse resp = ex.Response;
            using (StreamReader sr = new StreamReader(resp.GetResponseStream()))
            {
                Log.Error(sr.ReadToEnd(), ex, this);
            }
            base.RedirectOnItemNotFound(url);
        }
        catch (Exception ex)
        {
            Log.Error(ex.Message, ex, this);
 
            // If our plan fails for any reason, fall back to the base method
            base.RedirectOnItemNotFound(url);
        }
 
        // Must be outside the try/catch, cause Response.End() throws an exception
        context.Response.End();
    }
}
And that's it.

HTH,
Andreas

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013 anonymous access add attachments to list item

Image
Hi, Sometimes you want to enable anonymous access to be able to add a list item but at the same time attaching some documents. After good few hours playing around trying to make this work, turns out that we can achieve this functionality. The trick is to use RunWithElevatedPrivileges method for the file upload. We also want the file upload functionality to be available on the NewForm.aspx as it wouldn't make sense to put it in other forms as any user would be able to upload files to other records. The result will be something like this: When it is saved, the user is redirected to the display form: The close button then will take the user back to the homepage (or any page you desire) The steps: 1. Create an ascx control to host your file upload control in your project.  Put the below script in the ascx as well (credit to this post ): The code behind: 2. Create custom form template. You have to put the ascx in the CONTROLTEMPLATES folder of the ...
Read more

CRM Plugin - Parent and Child Pipeline

This concept tends to confuse people often - and I was no exception. I came across this problem when trying to create custom auto-numbering for one of my projects. Creating auto-number for Opportunity is easy. This is because the user creates opportunity straight from the home screen - thus the plugin runs on parent pipeline. However, it's a different story if you are dealing with Quote entity. Quote can be created in 2 ways, through the home screen OR the opportunity screen. If you create it from the latter, it will run on the child pipeline and you will find that your plugin will not work. Registering it as a child pipeline is easy, but CRM makes it harder since you can't use ICRMService. Instead, you have to create CRMService manually by using this piece of code: Not only that, with the child plugin you can't use Query expression to fetch other entities in your code unless you register it as ASYNCHRONOUS plugin. Mark Kovalcson in his blog found out that: A C...
Read more