[Mono-bugs] [Bug 75176][Nor] Changed - WebResponse.Close does not
immediately send the response
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Thu Jun 9 05:05:21 EDT 2005
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 gonzalo at ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=75176
--- shadow/75176 2005-06-08 15:03:07.000000000 -0400
+++ shadow/75176.tmp.11838 2005-06-09 05:05:21.000000000 -0400
@@ -1,13 +1,13 @@
Bug#: 75176
Product: Mono: Class Libraries
Version: 1.1
OS: unknown
OS Details:
-Status: NEW
-Resolution:
+Status: RESOLVED
+Resolution: FIXED
Severity: Unknown
Priority: Normal
Component: Sys.Web
AssignedTo: gonzalo at ximian.com
ReportedBy: lluis at ximian.com
QAContact: mono-bugs at ximian.com
@@ -63,6 +63,15 @@
due to the Sleep in the handler. But that Sleep is called after
Response.Close, so the client should not be affected by that wait.
Running the ashx in IIS (and the client on mono) gives the expected
results: the response is immediately closed and the client is not affected
by that wait.
+
+------- Additional Comments From gonzalo at ximian.com 2005-06-09 05:05 -------
+Printing the stacktrace in xsp under MS showed that CloseConnection
+was being called twice: one from Response.Close and another one after
+waiting those 10000ms from FinishRequest.
+
+Now we do the same.
+
+Thanks, Lluis.
More information about the mono-bugs
mailing list