Others will undoubtedly suggest this, but if you can, upgrade to the latest HttpClient 2.0 rc2. Numerous bug fixes for proxy support have been made since the release you mention. See if the newer release resolves the problem. If it doesn't, you might follow the instructions for troubleshooting on the web site, and let us know.
-Eric Johnson
Karr, David wrote:
I'm apparently using version "2.0-alpha3-dev" of HTTPClient.
I doubt this is a problem with HTTPClient, but I'm just trying to understand my issue a little better.
I have a servlet running in WebLogic on my desktop, and I'm trying to connect to an external URL through an authenticated proxy. My response from the connection gets a "502 Bad Gateway" error. I have another servlet with very similar code (and using the same HTTPClient version), but connecting to a different URL, running on a production box, which works fine.
Is this just a local problem with our proxy/firewall configuration, or something that I could be doing wrong in my code?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
