Java Web Start parses proxy autoconfiguration scripts very naively. It basically just greps for a "PROXY:" string and grabs the first proxy server it finds, without actually running the javascript logic. We should consider a better solution.
----------------
After extensive proxy detection modifications in tiger, we need to determine if we have lost any functionality in the other cases not adderssed.
1.) does proxy auto-detect now ALWAYS work on windows using IE.
2.) does it now ALWAYS work using other browsers (NS7) on windows.
3.) What is the current status on unix using NS or Mozzila ? we used to do as described above, and then show a dialog ( the first time ) asking user if these settings are ok.
###@###.### 2003-06-19
----------------
After extensive proxy detection modifications in tiger, we need to determine if we have lost any functionality in the other cases not adderssed.
1.) does proxy auto-detect now ALWAYS work on windows using IE.
2.) does it now ALWAYS work using other browsers (NS7) on windows.
3.) What is the current status on unix using NS or Mozzila ? we used to do as described above, and then show a dialog ( the first time ) asking user if these settings are ok.
###@###.### 2003-06-19
- duplicates
-
JDK-4802557 Consolidation: Networking/Proxy/Cookie
-
- Resolved
-
- relates to
-
JDK-4469455 proxy autoconfig script parsing has problems
-
- Resolved
-