On Mon, 2008-10-13 at 23:41 +0200, Oleg Kalnichevski wrote:
On Mon, 2008-10-13 at 10:45 -0700, Mohit Anchlia wrote:
What happens when an instance of HttpClient instance is created for
each request? Does it internally get associated with one Connection
manager or there is new connection
I'm torn! I'm using HttpClient in a Web application which uses the
authentication information from the Web app login to set credentials in the
HttpClient. I see that getState() is synchronized, but if I’m only using
one instance of the HttpClient in my web app, I could potentially send a
Oleg,
The problem also occurs with HttpClient 3.1. See below for updated log.
Let me know if you would want me to gather more information.
Thanks,
Henrich
...
11 DEBUG 06:56.34 Set parameter http.useragent = Jakarta
Commons-HttpClient/3.1
12 DEBUG 06:56.36 Set parameter http.protocol.version
On Tue, 2008-10-14 at 13:07 -0700, Henrich Kraemer wrote:
49 WARNING 07:04.26 Required proxy credentials not available for BASIC
any realm@proxy.ra.company.com:8080
Does this mean that your authentication has been initialized, but not
properly? Hence the error further down?
Christine
--
On Tue, 2008-10-14 at 09:58 +0200, Christine wrote:
On Mon, 2008-10-13 at 23:41 +0200, Oleg Kalnichevski wrote:
On Mon, 2008-10-13 at 10:45 -0700, Mohit Anchlia wrote:
What happens when an instance of HttpClient instance is created for
each request? Does it internally get associated with
On Tue, 2008-10-14 at 10:50 -0700, Brian Tanner wrote:
I'm torn! I'm using HttpClient in a Web application which uses the
authentication information from the Web app login to set credentials in the
HttpClient. I see that getState() is synchronized, but if I’m only using
one instance of the
On Tue, 2008-10-14 at 23:44 +0200, Oleg Kalnichevski wrote:
What is the tradeoff between using the same httpClient instance again
and again, or creating a new one on each request? Can you create a
memory leak by using one instance and not closing connections properly?
It very much
On Tue, 2008-10-14 at 23:51 +0200, Christine wrote:
On Tue, 2008-10-14 at 23:44 +0200, Oleg Kalnichevski wrote:
What is the tradeoff between using the same httpClient instance again
and again, or creating a new one on each request? Can you create a
memory leak by using one instance and
My understanding is that preemptive authentication mode does not require
credentials to be provided ahead of the request. The credentials in
HttpClients' state field are used if there are any that match the request.
In this app the credential-provider shows a dialog were the NTLM fields can
be
So what should be the protocol of shutting down cleanely: Below is the
sample code, does the below code look ok?
public class Test {
private static MultiThreadedHttpConnectionManager con = new
MultiThreadedHttpConnectionManager();
private static void doGet(HttpClient client) {
10 matches
Mail list logo
