JDK-6995917 : request not go through proxy correctly
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u22
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • CPU: x86
  • Submitted: 2010-10-28
  • Updated: 2011-09-27
  • Resolved: 2011-03-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
6-poolResolved 7Resolved
Related Reports
Duplicate :  
Here's the scenario:

1. User login to an authentication server which routes all the requests
   through a proxy, the app is then loaded
2. User run operations in the app

User encountered two problems depending on the JRE version and network options:

Problem 1:

 User is able to login to the authentication server but fails to load the app
 because some jars are not downloaded completely. This problem went
 away since 6u21. So this is not a real issue now.

Problem 2:

 When user perform one of the function in the app, the request is unexpectedly
 routed through PROXY=DIRECT instead of the actual proxy. As a result, the user
 encounters java.net.UnknownHostException which follows by a null-pointer

 The interesting part here is that with JRE 6u18, this problem is "workaround"
 by a running JVM with -Dhttp.keepAlive=false  (ie request correctly rounted
 through the actual proxy).  But in later JRE starting 6u19, the keepAlive
 workaround has no effect.

 The expectation is that the request should route through the actual proxy
 without any workaround on latest JRE (currently 6u22). So that after clicking
 the "reject" basket (step 11 below), the page reloaded with data.

Here's the test matrix:

JRE         keepAlive        result
6u18        T                problem 1
6u18        F                expected behavior

6u19        T                problem 1
6u19        F                problem 2

6u20        T                problem 1
6u20        T                problem 2

6u21        F                problem 2
6u21        F                problem 2

6u22        T                problem 2
6u22        F                problem 2

Please see comments for how to reproduce the problem, and
location of data collected by customer.

EVALUATION I could not reproduce the problem so far using JDK7. It seem that some of test password had expired and i can not follow all the steps listed to reproduce the issue. Please provide updated instruction how to reproduce the problem. Also, from details it seem that proxy info is missing whenever on demand network request is made. Could we get code snippet used to load the data that does not work? This should likely be ��implementation of fundtech.framework.CWebCommunication.send()