JDK-4469455 : proxy autoconfig script parsing has problems
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.
BugTraq+ Release Management Values
COMMIT TO FIX:
fix for hopper
On Windows, we should grab the COM JScript parsing engine and use it to parse
Because of limitations of the J2RE proxy implementation, the above is not
possible for Mantis. However, there are still steps that can be taken to
improve the proxy autoconfig script parsing implementation for Mantis:
1. Do not attempt to "guess" the proxy setting from an autoconfig script. If
we encounter a script, we should prompt the user to enter a proxy, with the
"hint" being what we saw in the autoconfig script.
2. Fix the Netscape 6 support so we now properly recognize an autoconfig setting
on Netscape 6.