[Mono-bugs] [Bug 75956][Nor] Changed - ASPSESSION cookie path incorrect

[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 bugzilla at patearl.net.

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

--- shadow/75956	2005-09-10 00:07:11.000000000 -0400
+++ shadow/75956.tmp.19996	2005-09-10 03:27:55.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 75956
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: RESOLVED   
-Resolution: NOTABUG
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: Sys.Web
 AssignedTo: gonzalo at ximian.com                            
 ReportedBy: bugzilla at patearl.net               
 QAContact: mono-bugs at ximian.com
@@ -52,6 +52,32 @@
   cookie.Path = UrlUtils.GetDirectory (context.Request.ApplicationPath);
 To:
   cookie.Path = context.Request.ApplicationPath;
 
 ------- Additional Comments From gonzalo at ximian.com  2005-09-10 00:07 -------
 The test in MS shows that what you expect is not what they do.
+
+------- Additional Comments From bugzilla at patearl.net  2005-09-10 03:27 -------
+I created a test situation with two applications in the following
+directories:
+
+/FSWebApps/TuboDril
+/FSWebApps/FSUserServiceAdmin
+
+Note that these directories were also configured as applications at
+the XSP command line.
+
+With the fix in place these apps function normally.  Without the fix,
+the session data from the applications somehow interferes.  Using the
+TuboDril application breaks the FSUserServiceAdmin application by
+affecting the Session data.
+
+Though I don't have access to an MS system to test, I wonder if the MS
+session data is somehow dependant on the URL being accessed, as well
+as the cookie.
+
+In any case, without the fix, I can't have two applications side by
+side without having them break each other.  I would ask you to
+reconsider if this is a bug, or if perhaps there is a related cause
+that MS has accounted for.  Whether MS has handled it or not, it
+certainly does not seem right that two separate applications should
+have the ability to break each other inadvertently.