Will you make a patch to the 2.x branch as well? The project I work
on currently uses the 2.0.1 implementation and we would rather avoid
having to change API to take advantageof this.
regards
Andre
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, S
Hi,
Has anyone done any experimentation to see if Java NIO could add anything
extra, performance wise, to HttpClient?
Andre
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I have set up a Tomcat 4.1 server to use SSL, with the help of a self-certified
certificate, ie with no trusted third party certifying it. I now try getting
my client, which uses 'commons-httpclient-2.0-rc2' to connect. When I do,
I get the following exception:
sun.security.validator.Valida
It shouldn't necessarily be ugly. The checks would be done by the authenticators
when they are inited for the first time. The factory simply takes care of loading
them, getting them to init and making them available. If the init() method of the
authenticator fails for whatever reason then it would
Okay, seems like I missed something and now I understand :) I should read further
before the knee jerk reaction.
I have just got my friend to try connecting to out intranet web server with
Safari and it does not support NTLM authentication. The only two web clients
on the platform that do suppor i
The only issue I would have of using a JNI solution, is that it would
work on MS-Windows, but break everywhere else. Being a client, we need
to have the flexibility to work no matter the platform. I have a
collegue
who has PowerBook which he uses on our Windows network, so this is such
a user a JNI
Interesting. Up to now I have been explicitly setting
the authorization header, because I couldn't get HTTP
Client to do what I wanted. In my case I just needed to
download a single resource from a URL given of the form:
http://user:[EMAIL PROTECTED]/
I didn't want to have to resend the reeques
Hi,
At the company I work for we are developing a middleware application
that routes SOAP messages from one party too another, using HTTP. I
have suggested that we use the MultithreadedConnectionManager, though
at the moment there is some reluctence. The issue seems to be because
we are potential
I am not really in a position to test the code, but could you see
whether changing the value of the 'user-agent' header gives:
method.setRequestHeader("user-agent",
"Mozilla/5.0 (Windows; U; Windows NT 5.0;
en-US; rv:1.6) Gecko/20040113");
or
method.setRequestHeader("user-agent",
