I think Svante is quite right. We needn't have 2 variants in the API -
HttpClient and HttpMultiClient. The API should transparently handle multiple
pools for different hosts instead of providing 2 different classes for
programmers. For most practical application multi client would anyway be the
on the same thing for
HttpMultiClient tomorrow and your code would help me understand what to
do.
I'll then make a patch including my and your changes and submit these so
that someone who is a committer on this project can add it to CVS.
Thanks,
Evert
On Tue, 2002-06-11 at 18:18, Sachin Hamirwasia
I think your problem is to do with the fact that the current version of
HTTPClient does not have proxy support for SSL connections. So when you try
to connect to an HTTP server via a proxy server, the HTTP client actually
makes an SSLSocket connection to the proxy server itself. But obviously
to the HTTPS server
without any proxies. Do I need a proxy to go through?
.sausheong
elipva Ltd
- Original Message -
From: Sachin Hamirwasia [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Sent: Wednesday, June 12, 2002 11:11 PM
Subject: RE: HttpClient with HTTPS
Hi,
Not sure if this has been discussed earlier, I have modified the
HttpClient's code slightly to make SSL work across a proxy server. Strange
enough, https proxy support was missing in the most current source code. If
it might be of interest to anyone, I can mail the code over.
Regards,
