JDK-4920526 : Needs per connection proxy support for URLs
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-09-10
  • Updated: 2017-05-16
  • Resolved: 2003-09-27
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 Availabitlity Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Related Reports
Relates :  
Relates :  
Description
The Java Deployment team needs support for per connection proxy in URLs for the following reason:

"When auto proxy script is specified, plugin needs to use no proxy to
download it, and in turns to use the script to evaluate proxy for future
connection. This works in the initialization phase even if no additional
API support. However, at any given time when the app is running, users
may detect to ask plugin/webstart to refresh the proxy. We will then
need to download the auto proxy script again with the ProxySelector
already installed. This is why I want per connection proxy. Also, applet
developers in the enterprise may want to make connection with a specify
proxy, so they don't have to worry about if the proxy in the client
machine is completely setup. " -- Stanley

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b22
2004-06-14

EVALUATION Will do for Tiger. ###@###.### 2003-09-10
2003-09-10