[Mono-bugs] [Bug 51841][Maj] New - Problem accessing Web Service using HTTP Basic Auth.

[bugzilla-daemon@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 davidandrewtaylor@hotmail.com.

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

--- shadow/51841	2004-02-05 20:24:57.000000000 -0500
+++ shadow/51841.tmp.553	2004-02-05 20:24:57.000000000 -0500
@@ -0,0 +1,72 @@
+Bug#: 51841
+Product: Mono/Class Libraries
+Version: unspecified
+OS: Red Hat 9.0
+OS Details: 
+Status: REOPENED   
+Resolution: 
+Severity: 004 Four hours
+Priority: Major
+Component: Sys.Web.Services
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: davidandrewtaylor@hotmail.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Problem accessing Web Service using HTTP Basic Auth.
+
+Description of Problem:
+I am trying to call a web service hosted on Apache Axis and configured to
+require HTTP Basic Authentication.  MONO does not appear to behave
+correctly when HTTP Basic Auth is required.
+
+Steps to reproduce the problem:
+1. Setup proxy authentication information.
+2. Call method on local web service proxy.
+
+Actual Results:
+Exception thrown shown below.
+
+Expected Results:
+MONO should supply the credentials on the second attempt when the server
+returns with the HTTP response for Auth-Required.
+
+Additional Information:
+
+MyService service = new MyService();
+// service.PreAuthenticate = true; // I tried both of true and false
+        
+// I also tried creating a credential cache....
+//CredentialCache cache = new CredentialCache();
+//cache.Add(new System.Uri(service.Url),"Basic", new
+NetworkCredential("user", "password"));
+//service.Credentials = cache;
+
+service.Credentials = new NetworkCredential("user", "password");
+service.callMyMethod("user");
+
+Unhandled Exception: System.Exception: Return code was: Unauthorized
+in <0x0012c>
+System.Web.Services.Protocols.SoapHttpClientProtocol:ReceiveResponse
+(System.Net.WebResponse,System.Web.Services.Protocols.SoapClientMessage,System.Web.Services.Protocols.SoapExtension[])
+in <0x0007d> (wrapper remoting-invoke-with-check)
+System.Web.Services.Protocols.SoapHttpClientProtocol:ReceiveResponse
+(System.Net.WebResponse,System.Web.Services.Protocols.SoapClientMessage,System.Web.Services.Protocols.SoapExtension[])
+in <0x0023b> System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke
+(string,object[])
+in <0x0006b> (wrapper remoting-invoke-with-check)
+System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke (string,object[])
+in <0x0005e>
+NotificationService.DeviceManagementService.DeviceManagementWSService:getDevicesByOwner
+(string)
+in <0x00058> (wrapper remoting-invoke-with-check)
+NotificationService.DeviceManagementService.DeviceManagementWSService:getDevicesByOwner
+(string)
+in <0x000f5> .test:Main ()
+
+------- Additional Comments From gonzalo@ximian.com  2003-12-12 01:00 -------
+Can you attach the headers that go from/to the server in the session?
+
+------- Additional Comments From davidandrewtaylor@hotmail.com  2004-02-05 20:24 -------
+Reopening but and will shortly post a test case.