hc-httpclient-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Milind Kadam <kadam.mil...@gmail.com>
Subject Re: JAVA Client on Windows 7 talking to ISS 6 with no HTTPs but Integrated Windows Authentication turned ON
Date Tue, 29 Nov 2011 15:40:38 GMT
Yes, because the browsers can access same URL; unless I am missing majorly
something.

--Milind



On Tue, Nov 29, 2011 at 10:35 AM, sebb <sebbaz@gmail.com> wrote:

> On 29 November 2011 14:18, Milind Kadam <kadam.milind@gmail.com> wrote:
> > Hi Oleg,
> >
> > I could get the ClientAuthenticaiton working after I moved my web server
> to
> > different machine. But after setting this web server behind firewall; I
> get
> > "Connection timed out: connect".
>
> That should be a big clue.
> It works without the firewall, and does not work with the firewall.
>
> So - have you set up the firewall to allow the connections?
>
> > Thanks in advance and any help appreciated.
> >
> > Here is the debug log:
> >
> > Trying:: 1
> > executing request GET
> https://mywebserver/cw_common/servlet/PMBuilderHTTP/1.1
> > 2011/11/28 16:24:01:348 EST [DEBUG] PoolingClientConnectionManager -
> > Connection request: [route: {s}->https://mywebserver][total kept alive:
> > 0;route allocated: 0 of 2; total allocated: 0 of 20]
> > 2011/11/28 16:24:01:348 EST [DEBUG] PoolingClientConnectionManager -
> > Connection leased: [id: 0][route: {s}->https://mywebserver][total kept
> > alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
> > 2011/11/28 16:24:01:551 EST [DEBUG] DefaultClientConnectionOperator -
> > Connecting to mywebserver:443
> > 2011/11/28 16:24:22:535 EST [DEBUG] DefaultClientConnection - Connection
> > org.apache.http.impl.conn.DefaultClientConnection@105bd58 closed
> > 2011/11/28 16:24:22:535 EST [DEBUG] DefaultClientConnection - Connection
> > org.apache.http.impl.conn.DefaultClientConnection@105bd58 shut down
> > 2011/11/28 16:24:22:535 EST [DEBUG] PoolingClientConnectionManager -
> > Connection[id: 0][route: {s}->https://mywebserver] can be kept alive for
> > 9223372036854775807 MILLISECONDS
> > 2011/11/28 16:24:22:535 EST [DEBUG] DefaultClientConnection - Connection
> > org.apache.http.impl.conn.DefaultClientConnection@105bd58 closed
> > 2011/11/28 16:24:22:535 EST [DEBUG] PoolingClientConnectionManager -
> > Connection released: [id: 0][route: {s}->https://mywebserver][total kept
> > alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
> > 2011/11/28 16:24:22:535 EST [DEBUG] PoolingClientConnectionManager -
> > Connection manager is shutting down
> > 2011/11/28 16:24:22:535 EST [DEBUG] PoolingClientConnectionManager -
> > Connection manager shut down
> > Exception in thread "main" org.apache.http.conn.HttpHostConnectException:
> > Connection to https://mywebserver refused
> >        at
> >
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:190)
> >        at
> >
> org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294)
> >        at
> >
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:636)
> >        at
> >
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:477)
> >        at
> >
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923)
> >        at
> >
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822)
> >        at
> >
> clientauthentication.ClientAuthentication.main(ClientAuthentication.java:76)
> >
> > Caused by: java.net.ConnectException: Connection timed out: connect
> >        at java.net.PlainSocketImpl.socketConnect(Native Method)
> >        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> >        at
> > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> >        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> >        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> >        at java.net.Socket.connect(Socket.java:519)
> >        at
> >
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:550)
> >        at
> >
> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:533)
> >        at
> >
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
> >
> >
> >
> > --Milind
> >
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Nov 15, 2011 at 10:03 AM, Oleg Kalnichevski <olegk@apache.org
> >wrote:
> >
> >> On Tue, Nov 15, 2011 at 09:59:33AM -0500, Milind Kadam wrote:
> >> > Yeah, I have seen that but then the question is why the URL works when
> >> > executed from both IE and FireFox browsers?
> >> >
> >> > --Milind
> >> >
> >>
> >> Because both applications can (and as far as I know actually do) use
> >> Windows platform specific APIs, which HttpClient being a pure Java
> library
> >> is not able to make use of.
> >>
> >> Oleg
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> >> For additional commands, e-mail: httpclient-users-help@hc.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message