Writing an ASP.NET custom error page
-
Hi Everyone, The company I work for has outsourced its website to a 3rd party, however we can write a custom error page to track 500 errors. We would like to be able to create such a 500 error page to find out as much as much as we possibly can about what happened to cause the 500 error. Also, we would like to get all the session and cookie data we can from the session that encountered the 500 error. Then, we'd like to save all of that data into a DB table. Have any of you done this sort of thing before, or have any recommendations? All the Best to You! :) Anne
-
Hi Everyone, The company I work for has outsourced its website to a 3rd party, however we can write a custom error page to track 500 errors. We would like to be able to create such a 500 error page to find out as much as much as we possibly can about what happened to cause the 500 error. Also, we would like to get all the session and cookie data we can from the session that encountered the 500 error. Then, we'd like to save all of that data into a DB table. Have any of you done this sort of thing before, or have any recommendations? All the Best to You! :) Anne
Session timeout in ASP.NET? Are you using Forms authentication? Forms authentication uses it own value for timeout (30 min. by default). A forms authentication timeout will send the user to the login page with the session still active. This may look like the behavior your app gives when session times out making it easy to confuse one with the other.
<system.web>
<authentication mode="Forms">
<forms timeout="50"/>
</authentication><sessionState timeout="60" /></system.web>
Setting the forms timeout to something less than the session timeout can give the user a window in which to log back in without losing any session data. thanks sign Lowongan Kerja
-
Hi Everyone, The company I work for has outsourced its website to a 3rd party, however we can write a custom error page to track 500 errors. We would like to be able to create such a 500 error page to find out as much as much as we possibly can about what happened to cause the 500 error. Also, we would like to get all the session and cookie data we can from the session that encountered the 500 error. Then, we'd like to save all of that data into a DB table. Have any of you done this sort of thing before, or have any recommendations? All the Best to You! :) Anne
I don't know if you will find this helpful, but I posted an article on this topic, after encountering a similar circumstance myself: ASP.NET Application Error Handling[^] ELMAH is another very good option - a popular choice among many developers: The Unsung Hero “ELMAH”[^]
-
Session timeout in ASP.NET? Are you using Forms authentication? Forms authentication uses it own value for timeout (30 min. by default). A forms authentication timeout will send the user to the login page with the session still active. This may look like the behavior your app gives when session times out making it easy to confuse one with the other.
<system.web>
<authentication mode="Forms">
<forms timeout="50"/>
</authentication><sessionState timeout="60" /></system.web>
Setting the forms timeout to something less than the session timeout can give the user a window in which to log back in without losing any session data. thanks sign Lowongan Kerja
Thanks, that is good to know. A third party wrote the code, so I am not sure. :) Anne
-
I don't know if you will find this helpful, but I posted an article on this topic, after encountering a similar circumstance myself: ASP.NET Application Error Handling[^] ELMAH is another very good option - a popular choice among many developers: The Unsung Hero “ELMAH”[^]
Thanks Daniel! I'll take a look at those resources. :) Anne