?So, The url is ssl enabled?
I found in my env that I had to manually set the proxy settings for Java explicitly until I noticed that the pac file pointed to a dns entry for the proxy server pointed to a CNAME, changed that to the technically correct A record and all the machines that required manual Java network overrides started working with the configuration cleared out. Without the manual Java network configuration, ssl enabled sties bypassed the proxy and attempted to route direct which of course was not available. jlc ________________________________ From: [email protected] <[email protected]> on behalf of Miller Bonnie L. <[email protected]> Sent: Friday, March 27, 2015 10:16 AM To: [email protected] Subject: [NTSysADM] Java and proxy.pac After many years, we are FINALLY rolling out a proxy.pac file for our browser settings-been testing with smaller groups of users, and has been fine. So today, we pointed a larger number of users to the file, and now have some calls about a specialized Java applet that is having issues. It's something that is part of our Student Information system that prints receipts for various items, so used by our Attendance offices and bookkeepers. After some searching, I think it may be that the Java applet is not reading the .pac file, but there seems to be some people who say you can make it work by doing x,y,z (not much detail) and others who say it simply can't read a .pac file at all. We've only tested IE, as apparently this app has never worked right in Chrome (which we also have). So, does anyone have their Java applets successfully using a pac file for proxy autoconfig, and if so, what is the trick? Or, is it a fact that it can't be done, and if so, what do you do instead? Ours is set up using an http url. Any assistance appreciated-please let me know if more detail is required on anything specific, as this is new territory. TIA, Bonnie
