Folks,
Here's a small patch that tweaks the default method retry handler a
little. Currently HttpClient 3.0 stubbornly reties method that fail due
to a timeout or an SSL handshake exception, which is not the way it
probably should be.
Unless I hear loud complaints, I'll apply the pat
the possible ways to work the problem around. A better solution would
be to make the certificate of the target server trusted. See
AuthSSLProtocolSocketFactory class for details
http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/src/contrib/org/apache/commons/httpclient/contr
Can you see what's wrong ? I also attach the trace file from WAS for SSL
related.
[9/8/04 7:53:53:114 EDT] 35b7cbd SystemErr R
javax.net.ssl.SSLHandshakeException: unknown certificate
[9/8/04 7:53:53:114 EDT] 35b7cbd SystemErr R at
com.ibm.jsse.bg.a(Unknown Source)
[9/8/04 7:
Francis,
HttpClient _should_ actually work as is with the latest IBM JDKs. Only
in our 'contrib' package we use Sun JDK specific classes.
If it is not the case please let me know. The exception stack trace
would help
Anyway, for detailed info on SSL customization please re
Title: HttpClient, SSL, Websphere 5.1, IBM JSSE
Hi there,
I would like to use SSL with HttpClient in WAS 5.1, it was running fine with in stand along program with SUN JSSE. But WAS come with IBM JSSE, so how can I configure HttpClient to use IBM JSSE.
Thanks in advance
certificate chains to the standard trust manager
Oleg
On Wed, 2004-07-07 at 18:22, Eric Johnson wrote:
> Andre,
>
> At a quick glance, it appears that there is one problem that I've
> experienced that the SSL guide doesn't seem to cover. Presumably, once
> you'
e:
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 foll
Andre,
At a quick glance, it appears that there is one problem that I've
experienced that the SSL guide doesn't seem to cover. Presumably, once
you've created your self-certified certificate, you added it to your
JVM's cacerts file using the keytool? I've found that a
Andre
This is a very common problem. Please consult 'Customizing SSL' section of the
HttpClient SSL guide for details on how the problem can be resolved
http://jakarta.apache.org/commons/httpclient/sslguide.html
Oleg
-Original Message-
From: Andre-John Mas [mailto:[EMAIL
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
gzilla/show_bug.cgi?id=29306
[CONTRIB] SSL authenticating protocol socket factory
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RE
gzilla/show_bug.cgi?id=29306
[CONTRIB] SSL authenticating protocol socket factory
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
gzilla/show_bug.cgi?id=29306
[CONTRIB] SSL authenticating protocol socket factory
--- Additional Comments From [EMAIL PROTECTED] 2004-06-09 19:23 ---
Folks, if nobody objects loudly, I'll commit the patch shortly. I'd still
appreciate someone's proof-reading the ja
gzilla/show_bug.cgi?id=29306
[CONTRIB] SSL authenticating protocol socket factory
--- Additional Comments From [EMAIL PROTECTED] 2004-06-05 13:30 ---
Mike,
> 1) The various INFO log messaged should probably be switched to DEBUG.
No problem. I'll convert INFO logs to DEBUG prior to
gzilla/show_bug.cgi?id=29306
[CONTRIB] SSL authenticating protocol socket factory
--- Additional Comments From [EMAIL PROTECTED] 2004-06-04 23:31 ---
Oleg,
I haven't tested any of the code, but from looking through it I only have two
suggestions:
1) The various INFO log messaged shou
gzilla/show_bug.cgi?id=29306
[CONTRIB] SSL authenticating protocol socket factory
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|--- |2.0
gzilla/show_bug.cgi?id=29306
[CONTRIB] SSL authenticating protocol socket factory
--- Additional Comments From [EMAIL PROTECTED] 2004-05-30 23:06 ---
Created an attachment (id=11699)
Patch (take 1)
-
To unsubscribe,
gzilla/show_bug.cgi?id=29306
[CONTRIB] SSL authenticating protocol socket factory
Summary: [CONTRIB] SSL authenticating protocol socket factory
Product: Commons
Version: 2.0 Final
Platform: Other
OS/Version: Other
Status: NEW
Se
Just like to thank everyone that helped me with the trouble I was having
with the http client. Everything worked out ok in the end.
Regards
Lee Francis Wilhelmsen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional command
resend the reequest a second
time in response to a challenge.
Andre
-Original Message-
From: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 9:16 AM
To: Commons HttpClient Project
Subject: RE: Posting XML over authenticated connection using SSL
Lee Francis,
Now
From: Lee Francis Wilhelmsen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 15:03
To: Commons HttpClient Project
Subject: RE: Posting XML over authenticated connection using SSL
> Since you appear to be passing a custom HttpState object to the
> HttpClient#executeMethod these lines o
I think the problem is that the realm is being specified. Trying using
null as the realm: httpState.setCredentials(null, "somehost", creds);
Mike
Lee Francis Wilhelmsen wrote:
Since you appear to be passing a custom HttpState object to the
HttpClient#executeMethod these lines of code have no ef
Since you appear to be passing a custom HttpState object to the
HttpClient#executeMethod these lines of code have no effect of what so ever on the
method's execution
client.getState().setAuthenticationPreemptive(true);
client.getState().setCredentials(realm, host, upc);
>
Try this instead
httpSta
19
To: Commons HttpClient Project
Subject: Re: Posting XML over authenticated connection using SSL
>> - The server responds saying not authorized with a realm value
>> - HTTP Client then resends the post using the credentitals
>> I have supplied (why doesn't it do this the
- The server responds saying not authorized with a realm value
- HTTP Client then resends the post using the credentitals
I have supplied (why doesn't it do this the first time?)
This is the standard behaviour. You can enable preemtive authentication.
Ok, so I found a setAuthenticationPreemptive(
Lee Francis Wilhelmsen wrote:
I can't find anything in the HTTP client API. I've been looking for an
setPreemtiveAuthentication(boolean) method. I guess it's not that
easy... how can I set preemtive authentication?
even Google knows:
http://www.google.com/search?hl=de&ie=UTF-8&q=site%3Ajakarta.apa
- HTTP Client then resends the post using the credentitals
I have supplied (why doesn't it do this the first time?)
This is the standard behaviour. You can enable preemtive authentication.
I can't find anything in the HTTP client API. I've been looking for an
setPreemtiveAuthentication(boolean) m
Kalnichevski, Oleg wrote:
I agree with Odi that incorrect Content-Length value appears to be the culprit.
I suggest you also file a bug report with IBM. Not setting the content
length correctly is a really gross violation of the HTTP 1.1 Protocol.
It makes reusing the same connection completely
ailto:[EMAIL PROTECTED]
Sent: Friday, May 14, 2004 14:42
To: Commons HttpClient Project
Subject: Re: Posting XML over authenticated connection using SSL
Lee Francis Wilhelmsen wrote:
> - The server responds saying not authorized with a realm value
> - HTTP Client then resends the post using
The task at hand is the following: I'm posting xml to a servlet on a
IBM server. The server sends me xml back. The serlvet is protected by
username/password and the connection is SSL. I have to parse the
returned xml and read a special tag value to see if there is more data
availab
Lee Francis Wilhelmsen wrote:
- The server responds saying not authorized with a realm value
- HTTP Client then resends the post using the credentitals
I have supplied (why doesn't it do this the first time?)
This is the standard behaviour. You can enable preemtive authentication.
org.apache.c
ack.
I'm running on Sun JRE 1.4.2_03 on Win2000.
The task at hand is the following: I'm posting xml to a servlet on a IBM
server. The server sends me xml back. The serlvet is protected by
username/password and the connection is SSL. I have to parse the
returned xml and read a specia
6:52:67:05:2C:EA:F2:3A:4F:65:F0:D8
-Original Message-
From: Ortwin Glück [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 3:44 PM
To: Commons HttpClient Project
Subject: Re: [newbie] SSL
bagas wrote:
Dear All,
I am sorry let me rephrase my question.
What I want to ask a
, 2004 3:44 PM
To: Commons HttpClient Project
Subject: Re: [newbie] SSL
bagas wrote:
> Dear All,
>
> I am sorry let me rephrase my question.
> What I want to ask are
> 1. How do I check and approve a certificate sent by a web server in
> h
Message-
From: Ortwin Glück [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 3:44 PM
To: Commons HttpClient Project
Subject: Re: [newbie] SSL
bagas wrote:
> Dear All,
>
> I am sorry let me rephrase my question.
> What I want to ask are
> 1. How do I check and approv
Hi Oleg, thanks for your reply,
Yes, I got a mail out on the jboss forums as well, but haven't had any luck
there yet. I have tried just using HttpsURLConnection to no avail. I did go
through the SSL troubleshooting guide on the httpclient site, but could
unfortunately not find a soluti
usted certificate found.
2. Can a HttpClient uses a certificate so that it can be verified by a
webserver that it trying to connect? If this can be done please give me
an example?
Thank You.
Regards,
Rahmat Bagas Santoso
Please check out the SSL guide
http://jakarta.apache.org/commons/httpc
Fredrik,
This problem is clearly not HttpClient related, hence you have not been getting a lot
of responses. HttpClient simply expects JSSE to be there and be properly configured in
order for the HTTPS support to be functional. Please take a look at the HttpClient SSL
guide paying special
Hi all, I got a questing regarding using HttpClient from an MDB inside
Jboss.
Normal http connections work fine, but whenever I try to connect to a host
using https I get a SocketException, claiming SSL is not available:
12:13:39,338 INFO [STDOUT] 2004-04-21 12:13:39,322 ERROR
Raj
> Commons-HttpClient/2.0beta2
(1) You are using an ancient version of HttpClient. For the Lord's sake, PLEASE
UPGRADE. HttpClient 2.0 final is long out
(2) Once again, did you do the test from the 'troubleshooting' section of the SSL
guide?
Oleg
-Original Mess
eta2[\r][\n]"
2004/04/20 02:31:43:326 CDT [DEBUG] wire - ->> "Host:
10.248.193.151[\r][\n]"
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
at com.sun.net.ssl.internal.ssl.InputRecord.b(DashoA6275)
at com.sun.ne
t side? What kind of web
server are you running on the server? What is the SSL library used by the server?
Oleg
-Original Message-
From: Raj, Bhalla [mailto:[EMAIL PROTECTED]
Sent: Monday, April 19, 2004 17:25
To: Commons HttpClient Project
Subject: RE: HttpClient for Https gives Unrecogniz
Hi Oleg,
Many thanks for response.
I am performing SSL test(I may not able to run Test class ) .Mean while a
quick question.
Could this happen coz of untrusted certificate from server.
But in my code i have using EasySSLProtocolSocketFactory.
Protocol.registerProtocol("https", ne
Raj,
Please note that HttpClient simply makes use of JSSE and does not attempt to provide
any sort of transport security by itself. As far as HttpClient is concerned SSL is
just a transport layer which is supposed to be completely transparent to HttpClient.
I'll do my best to help yo
rror as mentioned
Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
connection?
at com.sun.net.ssl.internal.ssl.InputRecord.b(DashoA6275)
at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA6275)
at com.sun.net.ssl.internal.ssl.SSLSocketIm
Raj,
Are you sure that SSL is configured on the server side? "Unrecognized SSL
message, plaintext connection?" exception is usually thrown when an attempt
is made to connect SSLSocket to a plain HTTP port
Oleg
>-- Original Message --
>Reply-To: "Commons HttpClient Proje
Hello Raj,
I take it that you are connecting to the following URLs:
http://10.248.193.151:80/services/tvly/mmh.cgi/
https://10.248.193.151:443/services/tvly/mmh.cgi/
which rules out my suspicion that you might be connected
to port 80 via SSL. Could you please try to generate a wire log?
http
ndling exception: javax.net.ssl.SSLException: Unrecognized SSL
message, plaintext connection?
Thread-10, SEND TLSv1 ALERT: fatal, description = unexpected_message
Thread-10, WRITE: TLSv1 Alert, length = 2
Thread-10, called closeSocket()
Thread-10, called close()
Thread-10, called closeInternal(true)
T
HttpClient for Https gives Unrecognized SSL message..
Hello Raj,
could you post a code example? I am a bit confused
about the "https for the same link" part. The protocol
is usually part of the link. If you managed to convice
HttpClient to use SSL, while the server still believes
it i
Hello Raj,
could you post a code example? I am a bit confused
about the "https for the same link" part. The protocol
is usually part of the link. If you managed to convice
HttpClient to use SSL, while the server still believes
it is plain HTTP, that would explain the error messag
he
browser. ).
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
at com.sun.net.ssl.internal.ssl.InputRecord.b(DashoA6275)
at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA6275)
t
Cc: Daniel C. Amadei
Subject: Re: [PATCH] SSL guide amendments (patch against 2.0 branch)
Oleg,
A few suggested edits I'm not a great editor myself (I
frequently
miss bevies of typos when my spouse asks me to review her writing),
but
since nobody else responded, I figured I would.
Hopef
nson [mailto:[EMAIL PROTECTED]
> >Sent: Thursday, April 15, 2004 15:18
> >To: Commons HttpClient Project
> >Cc: Daniel C. Amadei
> >Subject: Re: [PATCH] SSL guide amendments (patch against 2.0 branch)
> >
> >
> >Oleg,
> >
> >A few suggest
al Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 15:18
To: Commons HttpClient Project
Cc: Daniel C. Amadei
Subject: Re: [PATCH] SSL guide amendments (patch against 2.0 branch)
Oleg,
A few suggested edits I'm not a great editor myself (I frequently
Cc: Daniel C. Amadei
Subject: Re: [PATCH] SSL guide amendments (patch against 2.0 branch)
Oleg,
A few suggested edits I'm not a great editor myself (I frequently
miss bevies of typos when my spouse asks me to review her writing), but
since nobody else responded, I figured I would.
Hope
f throwing java.io.InterruptedIOException as expected. As a result if read
+ operation on a secure (SSL) connection times out (SO_TIMEOUT is set to a positive value) HttpClient
Replace starting from "As a result...", "HttpClient responds to this
exception b
java.io.InterruptedIOException as expected. As a result if read
+ operation on a secure (SSL) connection times out (SO_TIMEOUT is set to a positive value) HttpClient
+ mistakingly assumes that the connection was dropped and throws a recoverable HTTP exception: Error in
+ parsing the status
gzilla/show_bug.cgi?id=20089
Authentication fails with proxied SSL Connections
This bug depends on bug 25529, which changed state:
What|Old Value |New Value
Status|RE
gzilla/show_bug.cgi?id=20089
Authentication fails with proxied SSL Connections
This bug depends on bug 25529, which changed state:
What|Old Value |New Value
Status|RE
AIL PROTECTED]
Sent: Monday, February 16, 2004 13:08
To: Commons HttpClient Project
Subject: RE: SSL - poor performance
Hi!
OK, thanks for your help, I found a solution!
With the system property javax.net.debug=ssl I saw that the SSL sessions were not
cached. This is because the createSocket method
Hi!
OK, thanks for your help, I found a solution!
With the system property javax.net.debug=ssl I saw that the SSL sessions were not
cached. This is because the createSocket method in EasySSLProtocolSocketFactory always
creates a new SSLContext so that the SSL sessions cannot be reused and the
Hello Stephan,
basically anything is happening between these two points.
The certificate check is performed when the SSL connection
is established. After that, the connection is available for use
by the HTTP Client, which will then:
- send HTTP headers
- send POST data
- wait for the reply from
Stephan,
Most likely the problem has nothing to do with HttpClient as such. Please refer to the
'known problems' / 'troubleshooting' section of the HttpClient SSL guide to find out
whether the problem is related to some peculiarities of your JSSE / JDK / target
server
Hi,
I am using HttpClient (2.0RC3) to make HTTP requests over SSL.
At first I specified the keystore with the trusted certificates by the system
properties javax.net.ssl.trustStore=/path/to/keystorefile and
javax.net.ssl.trustStorePassword=password
The performance was good in this case but I
> The results of this testing has put me into a state of confusion
> regarding what httpclient's relationship is to the Java keystore.
> Can someone clarify how HttpClient
> works with respect to SSL, CA certs, server certs, and keystores?
Brad,
There's no _direct
Brad O'Hearne wrote:
The results of this testing has put me into a state of confusion
regarding what httpclient's relationship is to the Java keystore.
I short: There is *no* relationship between HttpClient and the Java
keystore. HttpClient is completely unaware of the unde
Hey all,
I am experiencing very strange behavior using HttpClient over SSL, and
I wondered if someone could enlighten me as to how it works.
Basically, I have a small app that uses HttpClient to contact a web
server over https. What the app does is unimportant, but I have been
playing around
Thanksss so much for the help...
Crescent
- Original Message -
From: "Michael Becke" <[EMAIL PROTECTED]>
To: "Commons HttpClient Project" <[EMAIL PROTECTED]>
Sent: Wednesday, January 14, 2004 11:35 AM
Subject: Re: HttpClient SSL Help!
> Hi Cr
Hi Crescent,
This is because the SSL cert on the server is self-signed or signed by
an unknown certificate authority. JSSE (the SSL library used by
HttpClient) by default only trusts those SSL certs that are signed by a
few authorities (i.e. Verisign, Thawte). Please take a look at Sun&#
Hi, there
While trying to use HttpClient for a SSL application, I encountered an exception, the
codes I used were as follows(the URL is made up here):
HttpClient client = new HttpClient();
HostConfiguration config = client.getHostConfiguration();
HttpsURL sslURL = new HttpsURL("
gzilla/show_bug.cgi?id=20089
Authentication fails with proxied SSL Connections
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RE
gzilla/show_bug.cgi?id=20089
Authentication fails with proxied SSL Connections
This bug depends on bug 25529, which changed state:
What|Old Value |New Value
Status|AS
Lionel PASQUIER wrote:
Well... I successfully connected to a https server that does not require certificate with httpClient: the ssl guide explain very well how to do this. But I did not spot anything about client authentication
There is not much.
Maybe I am blind, but I need help
Well... I successfully connected to a https server that does not require certificate
with httpClient: the ssl guide explain very well how to do this. But I did not spot
anything about client authentication
Maybe I am blind, but I need help! :)
Is it in the SSLContext.init() that I should
Lionel PASQUIER wrote:
Hello and Happy New Year!
Thanks, same to you...
I was just curious to know if httpClient supports ssl authentication with certificate and private key?
That is I want to use httpClient to connect to a web site with my private key /
certificate from a keystore.
Is it
Hello and Happy New Year!
I was just curious to know if httpClient supports ssl authentication with certificate
and private key?
That is I want to use httpClient to connect to a web site with my private key /
certificate from a keystore.
Is it possible?
I could not find a word about it in the
g here. I have
experienced inconsistencies in certificate chain verification across different JVMs. I
am pretty sure that SUN's Java 1.4 SSL trust manager differs from that of earlier
versions. My best guess is that the problem may have been caused by a JVM specific
quirk in the JSSE code.
activities.
Thanks.
--
Sincerely,
David Webb
Vice-President
Hurff-Webb, Inc.
http://www.hurff-webb.com
(904) 861-2366
(904) 534-8294 Mobile
Quoting Oleg Kalnichevski <[EMAIL PROTECTED]>:
> David,
> You may want to take a different approach and provide a custom SSL trust
> manage
David,
You may want to take a different approach and provide a custom SSL trust
manager (which in its crudest and ugliest form may be programmed to
simply trust all target servers)
Take a look at the 'Customizing SSL in HttpClient' section of the
HttpClient SSL guide at the followin
I have written a simple Java application to call a URL using Jakarta
HttpClient. The code works like a champ on my windows 2K development
workstation when accessing a URL the is protected by Siteminder (which
redirects to SSL for Authentication). The big difference is that when I try to
run
nection conn = url.openConnection();
...but when I use HttpClient like this (where httpContent = an XML data
block):
HttpClient client = new HttpClient();
post = new PostMethod("https://www.fake-site.com:444/";);
post.setRequestBody(httpContent);
client.executeMethod(post);
...I get th
quot;;);
post.setRequestBody(httpContent);
client.executeMethod(post);
...I get the following exception:
java.net.SocketException: SSL implementation not available
Now, in my research I know that this exception can be thrown for a
variety of reasons, such as a missing/defunct trust.store, missing
P
gzilla/show_bug.cgi?id=20089
Authentication fails with proxied SSL Connections
--- Additional Comments From [EMAIL PROTECTED] 2003-12-15 11:47 ---
Created an attachment (id=9577)
Wire log of a successful SSL+ basic proxy + NTLM host s
gzilla/show_bug.cgi?id=20089
Authentication fails with proxied SSL Connections
--- Additional Comments From [EMAIL PROTECTED] 2003-12-15 11:44 ---
This bug will be fixed by the patch for the bug #25529. I am attaching the wire
log of the successful authentication against an NTLM host via
ficateException
{
}
}
private static SSLSocketFactory getSocketFactory()
{
try
{
SSLContext context = SSLContext.getInstance("SSL");
context.init(null, new TrustManager[] {new TM()}, null);
return context.getSocketFactory()
ttpClient.java:5
> 29)
>
> Can anyone help with this? Would using EasySSLProtocolSocketFactory
> class fix this error?
>
> Thanks,
> Aaron
>
>
> -Original Message-
> From: Marcus Crafter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 12, 20
ctory
class fix this error?
Thanks,
Aaron
-Original Message-
From: Marcus Crafter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 8:43 AM
To: Commons HttpClient Project
Subject: Re: SSL-Connection to unstrusted host
H Sven, Roland,
There's an example socket factory
llo Sven,
>
> you will have to register your own secure socket factory.
> In that factory, you can establish SSL connections without
> verifying certificates. Alas, I don't remember whether such
> code is included in the examples or has been posted to the
> mailing list. But the
Hello Sven,
you will have to register your own secure socket factory.
In that factory, you can establish SSL connections without
verifying certificates. Alas, I don't remember whether such
code is included in the examples or has been posted to the
mailing list. But the topic itself pops up
Well, the subject says it all:
I'd like to connect to a host with an untrusted SSL-certfictate. When
trying to connect, i always get the following exception:
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException:
No trusted certificate foun
o first get the existing protocol, and
just read the scheme and port from that, replacing the ssl socket
factory.
The problem I'm having is that the return I'm getting from
"hostConfig.getProtocol()" is a null pointer.
I have code something like this:
d
just read the scheme and port from that, replacing the ssl socket
factory.
The problem I'm having is that the return I'm getting from
"hostConfig.getProtocol()" is a null pointer.
I have code something like this:
Http
80 -> Bad request
> Port 443 -> a bad Status line. A leading "HTTP" is missed
You need to know exactly what port your proxy is listening on. Do you know what type
of proxy you are using?
> If the bug is still pending, whats the way around ?
Have a look at the "Know
Hello Anu,
this is not really an HTTP client issue. The HTTP client just
uses an SSL socket obtained from an SSLSocketFactory.
The default implementation for SSL sockets is Sun's JSSE.
It uses it's own mechanism for presenting client certificates
if requested by the server. See also
.confs. On the Server are to Apache
installation. One runs as Proxie and uses SSL. The other is a Webserver without SSL.
So now I've to figure out, how to set the HttpClient Host and Proxy. and where to use
my "workaround-for-self-signed-certificate" Protocol-Class
>What's the conventionell way ? Just thought, that I have to login to the Proxy to
>come in
> contact with the server behind.
Sure. What is not really conventional is to use SSL to connect the a proxy. Usually an
HTTP agent connects to a proxy using regular (plain) HTTP and
> EasyX509TrustManager implements the javax.net.ssl.X509TrustManager-Interface ? Then
> I'll have to provide
> three methods: checkServer/ClientTrusted() and getAcceptetdIssuers().
>Correct ?
Yep,
Oleg
-
To unsubscribe, e-mail:
>>What's the conventionell way ? Just thought, that I have to login to the Proxy to
>>come in
>> contact with the server behind.
>Sure. What is not really conventional is to use SSL to connect the a proxy. Usually
>an HTTP agent
>connects to a proxy using re
>I agree with Oleg here. It seems this server is not configured as an
>SSL proxy.
May be at another port. There are running two Apache. One as Proxy, one as WebServer.
I'll try to find out the port-configuration.
I'm wondering, who creates that CONNECT-Statement ? Ask the C
Ulrich Freyer-Hirtz wrote:
You're right. I've had a look into the Http.confs. On the Server are
to Apache installation. One runs as Proxie and uses SSL. The other is
a Webserver without SSL. So now I've to figure out, how to set the
HttpClient Host and Proxy. and where to use my
1 - 100 of 191 matches
Mail list logo
