Ulrich,
Apparently your attachment got rejected by the mail server. Try posting it in ZIP
format.
> Can't get a connection. I'm new to HttpClient, so it can be also be my fault:
> Depending on the Port I choose for
> the Proxy I get two different errors:
>
> Port 80 -> Bad request
> Port 443
>Ulrich,
>
>You are trying to use a normal HTTP server as if it were a proxy. Of course, that
>cannot work.
>The server is absolutely correct about rejecting the request as syntactically
>incorrect (status code 400)
You're right. I've had a look into the Http.confs. On the Server are to Apache
>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 then uses that
conn
> 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 regular (plain) HTTP and then uses tha
[DEBUG] wire - -<< "Content-Type: text/html; charset=iso-8859-1[\r][\n]"
>
> Please contact your network administrator to find out what port the proxy server is
> listening on
>
> Oleg
>
>
> -Original Message-
> From: Ulrich Freyer-Hirtz [mailto
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
"workaround-for-sel
On Tue, 2003-08-05 at 18:07, Michael Becke wrote:
> 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
>
>> One thing I can't understand, is, where is the place for the customized
>> SSL-negotiation ? Is it in the class
>> "EasyX509TrustManager(null)" and where can I find that class or an example ? The
>> example "EasySSL..." from the
>> documentation doesn't compile without such EasyX509TrustManage
Kalnichevski, Oleg wrote:
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
>By default, JSSE only supports SSL certs that are signed by Verisign,
>Thawte and a few others. Self-signed certs (I'm guessing this is what
>you are using) require the custom SSLProtocol workaround.
>
>Mike
First, thanks for the help. I went some steps further, but have not reached the target
Oleg
-Original Message-
From: Ulrich Freyer-Hirtz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2003 3:30 PM
To: Commons HttpClient Project
Subject: AW: Proxied SSL connection
Apparently your attachment got rejected by the mail server. Try posting it in ZIP format.
Here it comes
> One thing I can't understand, is, where is the place for the customized
> SSL-negotiation ? Is it in the class
> "EasyX509TrustManager(null)" and where can I find that class or an example ? The
> example "EasySSL..." from the
> documentation doesn't compile without such EasyX509TrustManager.
Y
>I am afraid things are a bit more complicated than that. HttpClient
>always uses a plain socket to establish connection with a proxy. As far
>as I understand so do IE & Mozilla. I think what Ulrich is trying to do
>is to connect to the proxy using SSL, which is quite unconventional I
>have to say.
Oleg Kalnichevski wrote:
Mike,
I am afraid things are a bit more complicated than that. HttpClient
always uses a plain socket to establish connection with a proxy. As far
as I understand so do IE & Mozilla. I think what Ulrich is trying to do
is to connect to the proxy using SSL, which is quite unc
>Apparently your attachment got rejected by the mail server. Try posting it in ZIP
>format.
Here it comes as zip
Also I've some failure in configuration, it would be helpful, if someone could tell
me, that the code should work.
>You need to know exactly what port your proxy is listening on.
ust 05, 2003 2:15 PM
To: [EMAIL PROTECTED]
Subject: Proxied SSL connection
Hi all,
I'm in trouble with a proxied SSL connection. So I looked up the FAQ's and the
Bug-List, where I read that this was a know bug. In Release notes of HttpClient2.1
release Candidate 1, it is mentioned, t
Hello Christian,
It depends on what you want to do. SSL is meant to
establish a secure end-to-end connection, and the both
ends are *usually* the client and the backend server.
I wouldn't rule out the possibility to connect to the
proxy using SSL. But this will only secure the connection
to the p
et: Dienstag, 5. August 2003 14:29
An: Commons HttpClient Project
Betreff: RE: Proxied SSL connection
Ulrich,
The bug is still open as far as I can tell.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20089
What is exactly the nature of the problem you have been experiencing? Proxy SSL
Ulrich Freyer-Hirtz wrote:
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 Client the
Server : "What Protocoll do you have at Port 80?" ? I told the client
ning on
Oleg
-Original Message-
From: Ulrich Freyer-Hirtz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2003 3:30 PM
To: Commons HttpClient Project
Subject: AW: Proxied SSL connection
>Apparently your attachment got rejected by the mail server. Try posting it in ZIP
>format.
Hi all,
I'm in trouble with a proxied SSL connection. So I looked up the FAQ's and the
Bug-List, where I read that this was a know bug. In Release notes of HttpClient2.1
release Candidate 1, it is mentioned, that this bug was fixed.
Are there still problems in this field ? Are t
22 matches
Mail list logo
