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
> 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:
Ulrich,
I agree with Oleg here. It seems this server is not configured as an
SSL proxy. Apache is capable of handling SSL tunneling via CONNECT but
it appears to not be configured that way. Also I am wondering why you
are using NTLM authentication with Apache.
Mike
Kalnichevski, Oleg wrote
> 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
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
connections are known to have issues in three specific cases only:
- Combination of proxy authentication
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)
CEST [DEBUG] wire - ->> "CONNECT https://vkk.valtech.de:80 HTTP/1.1"
CEST [DEBUG] wire
