app.UseExceptionHandler("/Error"); doesn't work on POST methods.

[TanvirArjel]

I have configured ASP.NET Core default Exception Handler as follows:

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
            if (env.IsDevelopment())
            {
                app.UseBrowserLink();
                app.UseDeveloperExceptionPage();
            }
            else
            {
                app.UseExceptionHandler("/Error");
                //app.UseHsts();
            }
}

Whenever any error occurs in the GET methods, it is working as expected that is it is being caught and redirected to the Error() method.

Problem is that whenever any error occurs in the POST methods, it is not working as expected that is it is not being caught and redirected to the Error() method.

Here is sample code:

public class HomeController : Controller
{
       // GET: ContactInfo/Create
        public async Task<IActionResult> Create()
        {
           Convert.ToInt32("Hello");  // Intentional error
            return View();
        }

        // POST: ContactInfo/Create
        
        [HttpPost]
        [ValidateAntiForgeryToken]
        public async Task<IActionResult> Create(ContactInfo contactInfo)
        {
            Convert.ToInt32("Hello"); // Intentional error
            if (ModelState.IsValid)
            {
                return RedirectToAction(nameof(Index));
            }
            
            return View(contactInfo);
        }

         [HttpGet]
        [Route("/Error/{id?}")]
        public IActionResult Error(int? id)
        {
            if (id == 404)
            {
                return View("PageNotFound");
            }

            var feature = HttpContext.Features.Get<IExceptionHandlerPathFeature>();
           // Necessary staffs here

            return View();
        }
}

[Tratcher]

Only the path is re-written, not the method. You have your Error action marked as handling Get requests, not Post.

[Eilon]

You should be able to remove the [HttpGet] from the Error method because it is what's causing the unnecessary restriction.

[TanvirArjel]

@Tratcher @Eilon Yes! You are correct! I didn't notice that. Thank you so much.