I have an application (web1) which needs to make requests to another
application(web2) and am using HttpClient BasicAuthentication to do this.
After logging in web1's webpage, here I need to access web2 using
HttpClient.
Since this http access happens from web1 to web2, it needs authentication.
On Thu, 2010-06-17 at 00:52 -0700, Paul Brown wrote:
I'm seeing odd issues with HC 3.1 on Windows. The symptom is that the
receiving server will intermittently report a chunking error. Background on
the scenario:
- JDK 1.6 u20, 32-bit Windows
- HC 3.1 used by SolrJ for ingest from one
On Thu, 2010-06-17 at 10:47 +0200, Eric wais wrote:
I have an application which needs to make requests to another application
and am using HttpClient to do this. My application will have multiple users
at once using the application. The application that I need to connect to is
in the form of a
On Fri, 2010-06-18 at 12:51 +0200, Joan Balaguero wrote:
Hello Oleg,
Thanks for your response.
What I mean by removing keep alive strategy is the following. I have an
administration application with the following option:
[x] Keep alive http connection for [ ] seconds.
If the
Ok, then my 'getKeepAliveDuration' method should do:
1. If the user enters a 'keepAliveDuration' ( 0) -- return this value.
2. If the user does not check 'keep-alive', then:
2.1. if 'keep-alive' header exists -- return its value.
2.2. if not, return Integer.MAX_VALUE.
Is this right?
On Jun 18, 2010, at 3:29 AM, Oleg Kalnichevski wrote:
We have not had a confirmed case of data corruption by HttpClient for
many years. The trouble is we no longer support HttpClient 3.1, so I
personally doubt anyone would be willing to invest time and effort into
investigating the problem.
