Hi Oleg, Thanks for the quick response.
The live httpheader logs shows similar request/response header : HTTP/1.1 401 Unauthorized X-Powered-By: Servlet/3.0 WWW-Authenticate: Negotiate Content-Type: text/html; charset=UTF-8 Content-Language: en-US Content-Length: 149 Date: Sat, 23 Feb 2013 16:43:11 GMT Server: WebSphere Application Server/8.0 ---------------------------------------------------------- http://isfdevftp1.in.ibm.com:9080/ibm/iis/test/TestGetSession GET /ibm/iis/test/TestGetSession HTTP/1.1 Host: isfdevftp1.in.ibm.com:9080 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Cookie: JSESSIONID=00003WQG7Fbu4D-BtXGSAr5tUxK:-1; TJE=; TE3=; sessionCode=146731693 Connection: keep-alive Authorization: Negotiate YHsGBisGAQUFAqBxMG+gMDAuBgorBgEEAYI3AgIKBgkqhkiC9xIBAgIGCSqGSIb3EgECAgYKKwYBBAGCNwICHqI7BDlOVExNU1NQAAEAAACXsgjiBwAHADIAAAAKAAoAKAAAAAYBsR0AAAAPSVNGREVWRlRQMUlGU0NPUkU= HTTP/1.1 401 Unauthorized X-Powered-By: Servlet/3.0 WWW-Authenticate: Basic realm="IBM Information Server" Content-Language: en-US Content-Length: 0 Date: Sat, 23 Feb 2013 16:43:11 GMT Server: WebSphere Application Server/8.0 so the server is throwing the basic challenge incase of authentication failure, why is the HttpClient wire log not showing the second set of communication log and just closes the connection 2013/02/23 22:09:43:698 IST [DEBUG] DefaultClientConnection - Receiving response : HTTP/1.1 401 Unauthorized 2013/02/23 22:09:43:698 IST [DEBUG] headers - << HTTP/1.1 401 Unauthorized 2013/02/23 22:09:43:698 IST [DEBUG] headers - << X-Powered-By: Servlet/3.0 2013/02/23 22:09:43:698 IST [DEBUG] headers - << WWW-Authenticate: Negotiate 2013/02/23 22:09:43:698 IST [DEBUG] headers - << Content-Type: text/html; charse t=UTF-8 2013/02/23 22:09:43:713 IST [DEBUG] headers - << Content-Language: en-US 2013/02/23 22:09:43:713 IST [DEBUG] headers - << Content-Length: 149 2013/02/23 22:09:43:713 IST [DEBUG] headers - << Date: Sat, 23 Feb 2013 16:39:42 GMT 2013/02/23 22:09:43:713 IST [DEBUG] headers - << Server: WebSphere Application S erver/8.0 2013/02/23 22:09:43:713 IST [DEBUG] DefaultHttpClient - Connection can be kept a live indefinitely 2013/02/23 22:09:43:713 IST [DEBUG] DefaultHttpClient - Authentication required 2013/02/23 22:09:43:713 IST [DEBUG] DefaultHttpClient - isfdevftp1.in.ibm.com:90 80 requested authentication 2013/02/23 22:09:43:713 IST [DEBUG] DefaultHttpClient - Authorization challenge processed 2013/02/23 22:09:43:713 IST [DEBUG] SPNegoScheme - Received challenge '' from th e auth server 2013/02/23 22:09:43:713 IST [DEBUG] SPNegoScheme - Authentication already attemp ted 2013/02/23 22:09:43:713 IST [DEBUG] DefaultHttpClient - Authentication failed why there is difference in the challenge thrown between the browser and HttpClient? any clarifications would be helpful. Regards, Oleg -- View this message in context: http://httpcomponents.10934.n7.nabble.com/Making-HTTPClient-work-with-SPNEGO-authentication-tp19413p19473.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
