Dave,
You are not using HttpConnection class to establish connection with the
target server, are you?
Does you code look something like this?
HttpConnection conn = new HttpConnection(...);
conn.open();
HttpState httpstate = new HttpState();
GetMethod httpget = new GetMethod("https://www.whatever.com/";);
httpget.execute(conn, httpstate);
If it does, that would pretty much explain the problem, as the
connection management as well as proxy access are handled by HttpClient
class
If you want HTTPS tunneling to be taken care of automatically, you
should be using HttpClient class
HttpClient client = new HttpClient();
client.getHostConfiguration().setProxy(...);
GetMethod httpget = new GetMethod("https://www.whatever.com/";);
try {
client.executeMethod(httpget);
} finally {
httpget.releaseConnection();
}
I may still be wrong in my assumption, but that is the only thing I can
think of that can explain this kind of problem.
Oleg
On Thu, 2004-06-03 at 23:07, Dave Seidel wrote:
> We embed HttpClient in our product (SOAPscope), and some of our users have
> reported a problem accessing https URLs if they use a proxy server. I tried
> this, and can readily recreate the problem (I'm using Squid). I used
> TcpTrace to capture one of these requests, and compared it to the same
> request peformed by FireFox. The FireFox request gets becomes a CONNECT
> before it gets sent to the proxy, and it works fine. But the equivalent
> request from HttpClient just goes through as a GET and fails (since Squid
> won't handle a GET over https.
>
> What's the best way for me to fix this? Should HttpClient handle the
> conversion from GET or POST to CONNECT, or do I have to handle it myself in
> my client code (i.e., use ConnectMethod instead of PostMethod or GetMethod,
> based on isSecure() && isProxied())?
>
> - Dave Seidel, Mindreef, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
