[Mono-bugs] [Bug 70264][Nor] Changed - Xsp on windows is not setting content-length or FIN on reply.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 6 Dec 2004 19:06:49 -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 gonzalo@ximian.com.


--- shadow/70264	2004-12-06 17:18:23.000000000 -0500
+++ shadow/70264.tmp.1054	2004-12-06 19:06:49.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 70264
 Product: Mono: Class Libraries
 Version: 1.1
+OS: unknown
 OS Details: Windows XP
-Status: NEW   
+Status: ASSIGNED   
+Severity: Unknown
 Priority: Normal
 Component: Sys.Web
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: mlasky@novell.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -40,6 +40,18 @@
 Additional Information:
 ------- Additional Comments From mlasky@novell.com  2004-12-06 17:18 -------
 Created an attachment (id=13415)
 Ethereal capture file showing the problem.
+------- Additional Comments From gonzalo@ximian.com  2004-12-06 19:06 -------
+If we don't know the content length and using HTTP/1.0, which is
+forced by xsp standalone, we must send the 'Connection: close' header.
+This is also an issue for 1.1 connections without a content length and
+not using 'chunked' transfer encoding.
+Our System.Web can detect and 'fix' by sending the 'Connection: close'
+heder or figuring out the length, but seems like MS System.Web don't
+do this.
+I'll fix this in XSP.