The Verify Java Version page fails when going thru the newer MWG.
I have two MWGs.
Version 7.1.6.1.0(12742) works.
I don't anything special.
Version 7.4.1.3.0(17293) doesn't work.
I created a top level rule set just for the test PC with a Stop Cycle, still doesn't work.
I am logged into the PC as a domain admin.
IE 9 is installed.
Any ideas. I really need to get this to work on the new MWG.
Moved to Web Gateway By - Moderator
Check java version on client. last 1.7.71 nor 1.8.25 java versions do not sop port proxy. Seems to be bug. 1.7.67 works ok with MWG 7.4.x
What is SOP port proxy?
The java version is am testing with is 8.25.
But why does this test PC with java 8.25 work thru my older MWG Version 7.1.6.1.0(12742), but not thru my newer MWG Version 7.4.1.3.0(17293)?
I see it as an issue with the newer MWG.
SOP port is misstake 🙂
We use only standard http/https proxy on port 8080.
Seems that Java looks for for OS proxy settings which use script configuration via proxy.pac. If I am correct, the new versions of java do not parse correctly proxy.pac settings so it assumes direct connection to internet.
You can try manual proxy settings to specific IP and port.
Update:
Manual proxy settings does not work even. So we found only one Java version which can pass proxy: 1.7.67 😞
If I un-check "Use automatic configuration script and check proxy server and point to the same web proxy IP (port 9090). Java verifies.
Here is the PAC file path:
Java Verify failure unable to Configure Java Control Panel not opening ( Fix : )
Java Verify failure unable to Configure Java Control Panel does not open ( Fix : )
this is a regular ( windows 7 bug related ) problem after successful installation of Java ( jre ) and fresh installation of Windows7 64bit or 32bit on my laptop or desktop. what worked perfectly for me was setting COMPATIBILITYMODE=WINDOWSNT to make windows launch the JP2LAUNCHER.EXE and JAVAW.EXE files properly.
jp2launcher.exe windowsNT compatibilty solves Java Verify failure problem at https://www.java.com/en/download/installed.jsp
javaw.exe windowsNT compatibilty solves unable to open or Configure Java Control Panel problem.
* search for JAVAW.EXE inside c:\program files or c:\program files (x86)
* right-click mouse on JAVAW application icon logo
* click PROPERTIES
* click COMPATIBILITY
* tick the checkbox at COMPATIBILITY MODE
* choose WINDOWS NT service pack
* click APPLY or click OK
Now, the Configure Java Control Panel will start opening and working.
* search for JP2LAUNCHER.EXE inside c:\program files or c:\program files (x86)
* right-click mouse on JP2LAUNCHER
* click PROPERTIES
* click COMPATIBILITY
* tick the checkbox at COMPATIBILITY MODE
* choose WINDOWS NT service pack
* click APPLY or click OK
Now, the Verify Java will be successful at https://www.java.com/en/download/installed.jsp
if we find 2 or 3 versions of JP2LAUNCHER and JAVAW when we search, then we must repeat the above for all of them.
in the Configure Java Control Panel Advanced tab we can set "Do not check" certificate revocation and disable security verification.
and in the Security tab we may Edit Site List... for the Exception Site List ( add URLs to unblock sites )
The problem is not with Java Controll Panel. It works, I can modify settings (security, netowork etc.) but looking at firewall logs, I can see direct internet connection instead of using proxy server 😞
The same PC works OK with direct (mobile 3G/LTE) internet connection. Even I turn off proxy.pac config in IE and setup only manual proxy settings via proxy, Java still does not use proxy.
I will try some more steps.
There seems to be regression bug about pac file parsing: https://bugs.openjdk.java.net/browse/JDK-8064675
One workarround is use pac file only for MSIE and setup fixed proxy only for java via Configure Java control panel.
Hope I will get it working via better PAC file.
We are testing new proxy.pac file as workarround.
current pac file uses the logic:
if host is internal, return DIRECT else return PROXY
This does not work with current Java version at all because java stops parsing after first return line of script. in this case DIRECT
So new pac file does oposite logic:
if host is NOT internal, return PROXY else return DIRECT
In this reversed case, java parsing will stop after first return with value PROXY.
So this seems to be working pac file for Java 1.8. update 25:
function FindProxyForURL(url, host) {
// If the requested website is hosted outside the internal network, send proxy.
if (!(isPlainHostName(host)) &&
(!isInNet(dnsResolve(host), "127.0.0.1", "255.255.255.255")) &&
(!isInNet(dnsResolve(host), "10.0.0.0", "255.0.0.0")) &&
(!isInNet(dnsResolve(host), "192.168.0.0", "255.255.0.0")) )
return "PROXY proxy.domain.com:8080";
else
return "DIRECT";
}
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center
Corporate Headquarters
2821 Mission College Blvd.
Santa Clara, CA 95054 USA