You are viewing a plain text version of this content. The canonical link for it is here.
Posted to httpclient-users@hc.apache.org by bharathi swarajya <ss...@rediffmail.com> on 2005/12/28 02:17:59 UTC
Does HttpClient retain connection on explicit Server termination
Hi
I have some clarification regarding the HttpCLient mechanisam. When a server explicitly sends a termination request, how does HttpClient behave. Does it still reuse such kind of connections. will that be considered as a part of the pool.Could anyone help in this.
Thanks
S.S. Bharathi
On Wed, 28 Dec 2005 Oleg Kalnichevski wrote :
>On Tue, 2005-12-27 at 23:11 +0530, Nishant Agrawal wrote:
> > Thanks Oleg.
>...
> >
> >
> > -- If I send to 2 different servers (at 2 different URLs),
> >
> > -- how will implementation decide as to which manager to use, for
> > present key-cert combo to each server.
> >
> > -- here I assume that each different server recognizes this same client
> > application, by different identities.
> >
> >
> >
> > --For e.g.:
> >
> > --ClientApp has 2 keyManagers
> >
> > ---1. KeyManager_A ( key_a, certChain_a)
> >
> > ---2. KeyManager_b ( key_b, certChain_b)
> >
> > -- server_a identifies certChain_a only.
> >
> > -- server_b identifies certChain_b only.
> >
> >
>
>You have to configure different SSL contexts for these two servers. The
>easiest way to achieve that is to have a different key store per
>different identity
>
>Oleg
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: httpclient-user-help@jakarta.apache.org
>
Re: Does HttpClient retain connection on explicit Server termination
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Wed, Dec 28, 2005 at 01:17:59AM -0000, bharathi swarajya wrote:
> ?Hi
>
> I have some clarification regarding the HttpCLient mechanisam. When a server explicitly sends a termination request, how does HttpClient behave. Does it still reuse such kind of connections. will that be considered as a part of the pool.Could anyone help in this.
>
The HTTP protocol does not provide a mechanism to notify the
counterpart of the fact that the connection is about to be closed. Both
the client and server may close the connection at any time without prior
notice
Oleg
>
> Thanks
> S.S. Bharathi
>
>
> On Wed, 28 Dec 2005 Oleg Kalnichevski wrote :
> >On Tue, 2005-12-27 at 23:11 +0530, Nishant Agrawal wrote:
> > > Thanks Oleg.
> >...
> > >
> > >
> > > -- If I send to 2 different servers (at 2 different URLs),
> > >
> > > -- how will implementation decide as to which manager to use, for
> > > present key-cert combo to each server.
> > >
> > > -- here I assume that each different server recognizes this same client
> > > application, by different identities.
> > >
> > >
> > >
> > > --For e.g.:
> > >
> > > --ClientApp has 2 keyManagers
> > >
> > > ---1. KeyManager_A ( key_a, certChain_a)
> > >
> > > ---2. KeyManager_b ( key_b, certChain_b)
> > >
> > > -- server_a identifies certChain_a only.
> > >
> > > -- server_b identifies certChain_b only.
> > >
> > >
> >
> >You have to configure different SSL contexts for these two servers. The
> >easiest way to achieve that is to have a different key store per
> >different identity
> >
> >Oleg
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: httpclient-user-help@jakarta.apache.org
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-user-help@jakarta.apache.org