Handle 500 Exception in the Application

HttpBeginRequest Pipeline

The processors in the HttpBeginRequest pipeline generate and populate the Sitecore.Context class.

In my Application, We have the httpRequestBegin Pipeline with 30 processors.


When the httpRequestBegin pipeline is executed, the processors defined above run in order from first to last.

Handle the 500 Exception in web pages

Currently I can see the errors on my page. It’s not good to show to our live site.


Create a class file

 public class Handle500Exception: ExceptionProcessor

    {

        public override void Process(ExceptionArgs args)

        {

            try

            {

                ExceptionContent objex = new ExceptionContent();

                HttpContext httpContext = HttpContext.Current;

                httpContext.Server.ClearError();

                httpContext.Response.TrySkipIisCustomErrors = true;

                httpContext.Response.StatusCode = 500;

                httpContext.Response.Write(objex.GenerateExceptionPage());

            }

            catch (Exception ex)

            {

                Log.Info(string.Format("Process  -- error message -- {0}  stacktrace {1} ", ex.Message.ToString(), ex.StackTrace.ToString()), ex);

            }

        }

    }

 

    public class ExceptionContent

    {

        public string GenerateExceptionPage()

        {

            var context = System.Web.HttpContext.Current;

            string content = string.Empty;

            try

            {

                string domain = context.Request.Url.GetComponents(UriComponents.Scheme | UriComponents.Host, UriFormat.Unescaped);

                string errorPageLink = "/500";

 

                if (!string.IsNullOrEmpty(errorPageLink))

                {

                    content = Sitecore.Web.WebUtil.ExecuteWebPage(string.Concat(domain, errorPageLink));

                    Log.Error("Internal server error happened: " + context.Request.Url, this);

                }

            }

            catch (Exception ex)

            {

                Sitecore.Diagnostics.Log.Error("Error happened while generating ExceptionPage for 500 Error  :" + ex.Message, this);

                return string.Empty;

            }

            return content;

        }

 

    }

Create a config file

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:set="http://www.sitecore.net/xmlconfig/set/" xmlns:role="http://www.sitecore.net/xmlconfig/role/">

  <sitecore>

    <pipelines>

      <mvc.exception>

        <processor type="Sitecore.Mvc.Pipelines.MvcEvents.Exception.ShowAspNetErrorMessage, Sitecore.Mvc">

          <patch:attribute name="type">Sitecon.Project.CustomPipeline.Pipeline.Handle500Exception, Sitecon.Project.CustomPipeline</patch:attribute>

        </processor>

      </mvc.exception>

    </pipelines>

  </sitecore>

</configuration>

Create New 500 Page in Sitecore



Before publishing check the ShowConfig File 



After Publishing the class and config files to sitecore instance


Above config file has been overridden by my new config.


Try to hit the page Again



Sorry, I forget to publish my 500 pages to web database.














Comments

Post a Comment

Popular posts from this blog

Email Experience Manager (EXM)

Image
Email Experience Manager (EXM) To engage with customers in the website, we can deliver the relevant email messages to the customers at the right time. The Email Experience Manager (EXM) helps you create and deliver bulk email campaigns quickly and easily. The email campaign builder has four tabs each of which represents a step in the process. General On the General tab, you specify the campaign name and description along with the sender's details. Recipients On the Recipients tab, you add lists or segmented lists that you have created in the List Manager. You can also add a list of recipients that have been saved to a file. Message On the Message tab, you define the elements of the email message and this tab contains some important controls. Delivery On the Delivery tab, you have the choice to select the message variant and specify options and schedule.
Read more

Federated Experience Manager (FXM)

Image
The Federated Experience Manager (FXM) is an application that allows you to track visitor interactions and generate analytics information on external, non-Sitecore websites with Sitecore. You can use FXM to implement personalization rules, create goals and events, and implement content profiling on an external website. To enable FXM functionality, a JavaScript tag is added to the external websites. It allows the FXM application to connect the external site's components to the Sitecore Experience Platform. FXM has a dedicated Experience Editor that allows you to assign marketing attributes, implement personalization rules. You can access the FXM through the Marketing Control Panel or through the FXM application on the Sitecore Launchpad. When you have applied the FXM JavaScript tag to an external website, you can assign FXM functionality in one of the following ways: Capture Click Action Add Placeholder Add Page Filter Assign Marketing Attributes For reference :  https://vinayakchau...
Read more