{"id":6478,"date":"2017-05-29T03:05:37","date_gmt":"2017-05-29T03:05:37","guid":{"rendered":"http:\/\/www.gencayyildiz.com\/blog\/?p=6478"},"modified":"2017-05-29T03:05:37","modified_gmt":"2017-05-29T03:05:37","slug":"asp-net-mvc-ile-custom-error-pageozel-hata-sayfasina-yonlendirme","status":"publish","type":"post","link":"https:\/\/www.gencayyildiz.com\/blog\/asp-net-mvc-ile-custom-error-pageozel-hata-sayfasina-yonlendirme\/","title":{"rendered":"Asp.NET MVC \u0130le Custom Error Page(\u00d6zel Hata Sayfas\u0131na Y\u00f6nlendirme)"},"content":{"rendered":"
<\/div>\n

Merhaba,<\/p>\n

Asp.NET MVC mimarisiyle in\u015fa edilen projelerde beklenmedik olas\u0131 hatalar al\u0131nd\u0131\u011f\u0131nda yahut yap\u0131land\u0131r\u0131lmam\u0131\u015f, bozuk adreslere kullan\u0131c\u0131lar taraf\u0131ndan talepte bulunuldu\u011funda \u00f6ncelikle yapmam\u0131z gereken sistem taraf\u0131ndan f\u0131rlat\u0131lan hatay\u0131 kullan\u0131c\u0131ya g\u00f6stermeksizin kullan\u0131c\u0131y\u0131 \u00f6zel bir sayfaya y\u00f6nlendirmektir. \u0130\u015fte bu i\u00e7eri\u011fimizde bu i\u015flemin nas\u0131l yap\u0131laca\u011f\u0131n\u0131 ele alacak ve dikkat edilmesi gereken noktalar\u0131 vurgulayaca\u011f\u0131z.<\/p>\n

\u015eimdi d\u00fc\u015f\u00fcn\u00fcn; \u00fczerinde \u00e7al\u0131\u015ft\u0131\u011f\u0131m\u0131z projede kullan\u0131c\u0131 taraf\u0131ndan ge\u00e7ersiz bir adrese talepte bulunuldu\u011fu vakit nas\u0131l bir sonu\u00e7la kar\u015f\u0131la\u015f\u0131lmaktad\u0131r?
\n\"Asp.NET<\/a>
\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere “404 hatas\u0131” dedi\u011fimiz hatayla kar\u015f\u0131la\u015f\u0131lmaktad\u0131r.<\/p>\n

Bu ve buna benzer bir\u00e7ok olas\u0131 hata do\u011furabilecek durumlar i\u00e7in a\u015fa\u011f\u0131daki talimatlar\u0131 izleyerek \u00f6zel hata sayfan\u0131za y\u00f6nlendirmede bulunabilirsiniz.<\/p>\n

\u00d6ncelikle yapman\u0131z gereken, hatay\u0131 kar\u015f\u0131layacak olan “Error(Controller).cs” isminde bir controller olu\u015fturman\u0131zd\u0131r.(Controller’\u0131n ad\u0131n\u0131 konuyla alakadar olmak \u015fart\u0131yla istedi\u011finiz \u015fekilde belirtebilirsiniz.<\/em>)<\/p>\n

\r\n    public class ErrorController : Controller\r\n    {\r\n        public ActionResult PageError()\r\n        {\r\n            Response.TrySkipIisCustomErrors = true;\r\n            return View();\r\n        }\r\n        public ActionResult Page404()\r\n        {\r\n            Response.StatusCode = 404;\r\n            Response.TrySkipIisCustomErrors = true;\r\n            return View("PageError");\r\n        }\r\n        public ActionResult Page403()\r\n        {\r\n            Response.StatusCode = 403;\r\n            Response.TrySkipIisCustomErrors = true;\r\n            return View("PageError");\r\n        }\r\n        public ActionResult Page500()\r\n        {\r\n            Response.StatusCode = 500;\r\n            Response.TrySkipIisCustomErrors = true;\r\n            return View("PageError");\r\n        }\r\n    }\r\n<\/pre>\n
Yukar\u0131daki kod blo\u011funda g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi “Error(Controller).cs” i\u00e7erisine akl\u0131ma gelen t\u00fcm hatalar\u0131 kar\u015f\u0131lamay\u0131 sa\u011flayacak action metotlar\u0131 olu\u015fturdum.(Tabi ki de siz daha fazlas\u0131n\u0131 olu\u015fturabilirsiniz.<\/em>)<\/p>\n
T\u00fcm actionlar “PageError” sayfas\u0131na d\u00f6n\u00fc\u015f yapaca\u011f\u0131 i\u00e7in “PageError.cshtml” sayfas\u0131n\u0131da a\u015fa\u011f\u0131daki gibi olu\u015fturuyorum.<\/p>\n
\r\n<h2>Sayfa bulunamad\u0131...<\/h2>\r\n<div>\r\n    Hata Kodu : @Response.StatusCode\r\n<\/div>\r\n<div>\r\n    Hata Sebebi : @ViewBag.Kaynak\r\n<\/div>\r\n<\/pre>\n
Bu i\u015flemden sonra ana dizindeki Web.config dosyas\u0131n\u0131 a\u00e7\u0131n\u0131z ve <system.web>…<\/system.web> nodelar\u0131 i\u00e7erisine a\u015fa\u011f\u0131daki kal\u0131b\u0131 yerle\u015ftiriniz.<\/p>\n
\r\n.\r\n.\r\n.\r\n  <system.web>\r\n    <customErrors mode="On">\r\n      <error statusCode="404" redirect="\/Error\/Page404"\/>\r\n    <\/customErrors>\r\n    <compilation debug="true" targetFramework="4.6.1"\/>\r\n    <httpRuntime targetFramework="4.6.1"\/>\r\n  <\/system.web>\r\n.\r\n.\r\n.\r\n<\/pre>\n
Dikkat ederseniz burada “customErrors” nodeu ile \u00f6zel hata kontrol\u00fcn\u00fc devreye sokmu\u015f bulunuyoruz. “error” nodu ile de “statusCode” u 404 olan hata i\u00e7in “\/Error\/Page404” sayfas\u0131na y\u00f6nlendirmede bulunuyoruz.<\/p>\n
Bu i\u015flemden sonra projemizi derleyip \u00e7al\u0131\u015ft\u0131ral\u0131m ve bilin\u00e7li olarak 404 hatas\u0131n\u0131 alarak s\u00fcreci yeniden g\u00f6zlemleyelim.<\/p>\n