[Mono-bugs] [Bug 81853][Wis] New - session_end not fired

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by adriaanvk at gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=81853

--- shadow/81853	2007-06-11 06:08:34.000000000 -0400
+++ shadow/81853.tmp.17768	2007-06-11 06:08:34.000000000 -0400
@@ -0,0 +1,43 @@
+Bug#: 81853
+Product: Mono: Runtime
+Version: 1.2
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: adriaanvk at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: session_end not fired
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+
+
+Steps to reproduce the problem:
+1. create an aspx with only the code: Session.Abandon();
+2. create an handler in global.asax for Session_End
+3. 
+
+Actual Results:
+Session_End is never reached, but in MS.net it will. I am using the default
+sessionstate (no stateserver but the default inproc)
+
+Expected Results:
+Session_end is reached
+
+How often does this happen? 
+always
+
+Additional Information:
+I see a bug fix on mono:
+http://lists.ximian.com/pipermail/mono-patches/2007-February/087986.html
+I think this is a bad fix, because when reverting this, the Session_End is
+reached as in MS.net. Why is this fix done in feb 2007?