[Mono-bugs] [Bug 70206][Nor] New - xsp does not send a proper WSDL for a WebService

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 3 Dec 2004 22:05:00 -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/70206	2004-12-03 22:05:00.000000000 -0500
+++ shadow/70206.tmp.26339	2004-12-03 22:05:00.000000000 -0500
@@ -0,0 +1,53 @@
+Bug#: 70206
+Product: Mono: Class Libraries
+Version: unspecified
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: Sys.Web
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: gonzalo@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: xsp does not send a proper WSDL for a WebService
+[From Mike Lasky in bug 70123]
+There has been a new bug introduced with the latest changes to 
+System.dll and Xsp.exe.
+I am running on NLD (SLES 9.0) with the mono 1.1.2 rpms. I have 
+added the new System.dll and Xsp.exe from head (got from head on 
+The new System.dll is 
+in /usr/lib/mono/gac/System/1.0.5000.0__b77a5c561934e089.
+The new xsp.exe is in ~/mono/xsp/server.
+I put the test web service (WebTest.asmx and WebTest.dll) that we 
+sent you previously and that are attached to this bug in the web and 
+web/bin directories respectively.
+I have run xsp.exe with the following command: 'mono 
+~/mono/xsp/server/xsp.exe --applications /test:web --port 8086'
+I then hit the web service with a browser 
+at: 'http://localhost:8086/test/WebTest.asmx'.
+Xsp responds with the same chunk of data over and over until the 
+content length is satisfied and the client stops receiving.
+Please see the newly attached capture file called: Xspwsdl.cap for 
+the details.
+We are also seeing strange behaviour on the Windows iFolder client 
+where the error reported is that the XML data that was received by 
+the web service is malformed. I haven't been able to reproduce 
+consistently enough on Windows to track it down and make sure that 
+it is the same problem. However, the symptoms point to the same