Sorry, I had a bit of troubling grasping the question in my head, so it didn't come out too clearly.
On the client side, I'd like to send a request that I know will require credentials. So I get the HttpClient's credentialsProvider & set some credentials in it. I'd also like to open a GET request with a 'Connection: Close' header, but I know the GET is going to have the interim credentials exchange. Will the 'Connection: Close' that's added to the outgoing GET cause a server to close the connection before the authentication finishes? (This question is mostly a 'server behavior' question, but I'm not sure what the correct behavior should be.) If a properly behaved (or typically behaved) server will close the connection before the auth finishes, then the next question is: How do I add the Connection: Close into the subsequent GET that's performed internally by HttpClient after the auth finishes? What trick would I use in an interceptor in order to get the subsequent GET? Thanks! Sam On Tue, Jan 13, 2009 at 2:33 PM, Oleg Kalnichevski <[email protected]> wrote: > Sam Berlin wrote: >> >> Hi All, >> >> Is there a preferred way of adding a "Connection: Close" header into >> an exchange you expect (and want) to use credentials with? I would >> expect if the initial request had a failure due to unauthorized >> credentials that the Connection: Close would kill the connection >> instead of continuing the exchange of the credentials. If this is the >> case, is there a way to add Connection: Close to the request only >> after credentials are added? >> > > Hi Sam > > I am not sure I understand the problem entirely. Are you talking about > client-side or server-side processing? Anyways, a simple protocol > interceptor should do the job quite easily. > > Oleg > > >> Thanks. >> >> Sam >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
