[Mono-bugs] [Bug 50922][Maj] New - SessionInProcHandler is unstable

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 13 Nov 2003 01:16:52 -0500 (EST)


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 ximian@aksi.mdamt.net.

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

--- shadow/50922	2003-11-13 01:16:52.000000000 -0500
+++ shadow/50922.tmp.30292	2003-11-13 01:16:52.000000000 -0500
@@ -0,0 +1,47 @@
+Bug#: 50922
+Product: Mono/Class Libraries
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: System.Web
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: ximian@aksi.mdamt.net               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: SessionInProcHandler is unstable
+
+Description of Problem:
+two issues:
+[0]
+SessionInProcHandler is unstable. Internal datastructure is reinitialized
+in a webserver thread, so any data stored before will be null. (Init method)
+
+[1]
+Cookie returned by UpdateContext method doesn't have Path information
+required by RFC2019. 
+
+Steps to reproduce the problem:
+1. run the attached test case
+
+Actual Results:
+issue [0]: sometimes the sessionID will change if we reload the page
+issue [1]: if we run the test case in another directory, the cookie saved
+by the browser always have '/' as the path component of the cookie.
+
+Expected Results:
+issue [0]: the sessionID should be always the same
+issue [1]: cookie must contain path info so the browser will send the right
+cookie to the server according to the path of the request
+
+How often does this happen? 
+issue [0]: often
+issue [1]: always
+
+Additional Information:
+tried with xsp and our own aspx apache module