Support for HTTP BASIC authentication without redirect/HTTP 401

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Load a WSDL for a SOAP provider that requires HTTP BASIC authentication, but 
does not necessarily 
respond with a 401
2. Attempt to connect
3. Application crashes

What is the expected output? What do you see instead?

In this case we are connecting to an application that runs in a 'mixed' 
environment. In the event of failed 
logins it is not always able to distinguish between a user with a browser or a 
machine user doing HTTP and 
instead of responding with a 401 it will respond with a 302 redirecting to an 
HTML login page. SOAP Client 
crashes on this.

What version of the product are you using? On what operating system?
SOAP Client 1.6.3.1 on OS X 10.5.7

Please provide any additional information below.

Obviously we are working to correct the provider application behaviour. We 
control and want it to be a 
good netizen and return the correct HTTP response codes for a given 
circumstance. In the mean time we 
have been able to hit it using other applications (mostly cUrl) with HTTP basic 
and including that data in 
the initial request instead of waiting for a 401 and then resending with 
authentication. Being able to send 
the authentication in the first request is also much more efficient.

I have tried to set the HTTP authentication headers (by typing the header name 
into the header dropdown) 
and then copying in the base-64 encoding of the username and password. As near 
as I can tell this does 
not work. I will be firing up tcpdump to see if it is actually sent. 

Original issue reported on code.google.com by Jonathan...@gmail.com on 20 Jun 2009 at 4:49

[GoogleCodeExporter]

I would be interested in helping to correct this issue, but some guidance in 
understanding the relevant area of 
the application would help me get started.

Original comment by Jonathan...@gmail.com on 20 Jun 2009 at 4:50