I have enabled customError in my web.config file and it handles 'Page not found' error for aspx pages or any other files types handled by ASP runtime. My problem is my application is on a remote host and when a user tries a url on my website that ends with something other than those files types handled by ASP run time, for example http://mywesites.com/sdkdhiufuhief.hei, it displays a detailed error page by the IIS which I really don't like the malicious users to see. It contains a lot of information like the physical path of the application.
How can I handle all 404 html error regardless of the file type and URL in my ASP.NET application?
View Complete Post