![.net reflector 9 key .net reflector 9 key](https://d4.alternativeto.net/5Wv_WP0s1sFEukKQ_TAWXXpV_7Brm0PoGCjNaSjYqh4/rs:fill:400:400:0/g:ce:0:0/YWJzOi8vZGlzdC9zL2V4cGxvcmVyLXN1aXRlXzM2ODc0Ml9mdWxsLmpwZw.jpg)
![.net reflector 9 key .net reflector 9 key](https://i.ytimg.com/vi/3IvcXZVQ4CA/hqdefault.jpg)
When it came to me like a bug, I found that it is pretty simple and we can easily do that having the below patch. So far, there was no problem at all but it returned back to our team in UAT testing because it was returning 200 instead of the proper error code.
![.net reflector 9 key .net reflector 9 key](https://www.red-gate.com/simple-talk/wp-content/uploads/2010/02/ActivationStep2_TrialDialog_thumb.png)
Our team has already developed those pages by following this article > We develop a few error pages like 404, 500 and custom error pages. We have very specific issues for custom error pages. Once all the above changes are made content/business editors can configure this rule to personalize the components from experience editor or content editor from presentation->Personalize section.Now assign the Rules Tag (created in step 1) to the new Condition’s Default Tag under /sitecore/system/Settings/Rules/Definitions/Elements/URL/Tags/Default.Base template for my rule is “/sitecore/templates/System/Rules/Condition”.Under the Element Folder, we have to create our custom rule.Base Template : /sitecore/templates/System/Rules/Taxonomy/Element Folder.Next, you’ll need to add a new Element Folder under /sitecore/system/Settings/Rules/Definitions/Elements.Please note based template should be “/sitecore/templates/System/Rules/Taxonomy/Tag”.Create a new Rules Tag for the Conditions under /sitecore/system/Settings/Rules/Definitions/Tags.Based on the URL, he wants to display some renderings. Our client basically asked to have a personalised rule for URL. Based on our client requirements, I wrote the below-personalized rule. Creating personalization is really very simple and easy.