Add a CustomErrors section to your web.config.
1 Note the remoteonly will behave such that if you access the site from the local lan/intranet then it will not perform the redirect. The reason for this is so local developers and see the actual exception occuring while those accessing it from the public will see the ErrorPage. Aspx – AaronLS Oct 15 '10 at 20:40.
Yes the customErrors section of the web.config. This will redirect your users to what defaultRedirect (URL) when they encounter an error. You can also specify where they go based on the HTTP response code Here is the documentation.
1 +1 for in depth with doc link – Michael Wheeler Oct 15 '10 at 20:36.
It's not suitable for real use prior to . NET3.5 service pack 1, as until then the redirectMode attribute wasn't there and it would always act with the default value "ResponseRedirect" which would redirect to the error page instead of showing it directly; so instead of giving an error response it would "successfully" redirect to another page, and then that would return the error!
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.