Skip to main content
May 27, 2015
Question

Download issues with proxy using a proxy.pac file for configuration

  • May 27, 2015
  • 4 replies
  • 8888 views

I am having issues downloading/installing the Flash Player. The download of the small installer itself from the webpages works. But then the installer is not able to donwload the Flash player using a proxy server. If I set the Internet Explorer to use a proxy server, it works. If I set the Internet Explorer to use a proxy.pac file for connecting to the proxy server it does not work

This topic has been closed for replies.

4 replies

Participant
July 9, 2015

We've run the installer on a half dozen machines and it worked on all of them. And it shows up as being the current release when we check it at Adobe - Flash Player.

Noting that there's a strange "You may need to rest...." message displayed on the installer when it finishes up.

AnindyaS
Participating Frequently
July 10, 2015

Glad to see that it works on your machine.

Yes, that's the new message and looks like based on your resolution you are not seeing the complete message. If you hover on to it you can see the complete message in tooltip. The complete message is "You may need to restart your browser."

We are fixing the message truncation issue in next release.

-Anindya

Participant
June 12, 2015

Thank you for addressing this quickly.

Disabled AV, then this beta installed fine. Noting that the progress bar was just 3/4 of it's journey when it declared the installation was complete, FYI.

AnindyaS
Participating Frequently
June 13, 2015

Thanks Barbless for confirming.

Hi samd1959,

Can you send the error again which you are seeing, I am not seeing any error in your post.

Thanks for validating!

-Anindya

June 24, 2015

Hello!

What is the status of this issue? Is there any chance to get this fixed soon?

Regards,

Ulrich

Participant
June 10, 2015

Plus 1 for samd1959's research and conclusion. We have exactly the same issue he describes, with exactly the same symptoms seen in packet captures. Also verified that replacing the proxy .pac file with a proxy IP and port, "solves" the problem. But the problem is not with the proxy or the .pac, it's that these particular updates (17 and 18) are not working with the .pac file.

None of our users are able to update Flash, and we have no workaround since the fix requires abandoning the .pac file and adopting IP/port addressing, and our cloud-based proxy does not support that.

AnindyaS
Participating Frequently
June 11, 2015

Thanks for the comments and insights. We are working on the issue and I will update here.

Thanks,

Anindya

AnindyaS
Participating Frequently
June 12, 2015

Hello All,


Looks like we have found the issue and have a fix for that.  Can you please pick the new beta build from below location and try in your proxy environment with pac? If this work, then we will work on a release schedule to roll out the fix to production.

Thanks a lot for the help. This  beta version is for Flash Player 18 for IE browser.


Location to download beta build with proxy pac fix:  http://beta.acdcnext.com/flashplayeraxau.exe


P.S.: Please note that this is a beta build and may not be bug free and might not work as a normal release Flash player Installer. please test this in a limited environment on one machine. The purpose of sharing this ahead of release is to get more feedback on the proxy issue. Please do not pass on the link file or installer further.


Thanks,

Anindya

June 8, 2015

Having exactly the same issue.  Up until 05/26 there were no reported problems downloading/installing Flash Player with system settings using a PAC file (This is the standard config for our desktops).  Specifically the issue is the installer flashplayer17_ha_install.exe runs and is not using the PAC file when initiating a connection to get.adobe.com.  This looks like a bug that Adobe needs to address.

AnindyaS
Participating Frequently
June 9, 2015

Hi Samd1959,

We tested and found the download and install working fine with the pac file proxy configuration in our lab setup. It looks like we are not able to recreate the proxy/pac setup which you are having. It would be of great help in debugging the issue more if we get more information of the kind of proxy settings (and pac file) which you are using. If possible from you side we can do a quick call and screen share session with you to see the issue on the effected machines.

Thanks,

Anindya

June 9, 2015

Hello!

Maybe this issue is related to the complexity of the proxy.pac file.

We are using basically the following syntax:

function FindProxyForURL(url, host)

    {

// init variables

var proxy_yes = "PROXY proxy:8080";

var proxy_no = "DIRECT";

var retStr = "";

var resolved_ip = "";

// hostname to lowercase

var lhost = host.toLowerCase();

host = lhost;

// localhost directly

if ((host == "localhost") || (shExpMatch(host, "localhost.*")) || (host == "127.0.0.1"))

  retStr = proxy_no;

// Intranet hostnames directly

if (shExpMatch(host, "*.sk*.semikron.com") && retStr == "")

  retStr = proxy_no;

// plain host names directly

if (isPlainHostName(host)  && retStr == "")

  retStr = proxy_no;

// all others: resolve IP and match IP address against internal networks

if (retStr == "")

  resolved_ip = dnsResolve(host);

  if (isInNet (resolved_ip, "172.16.0.0", "255.255.0.0"))

   retStr = proxy_no;

if (retStr == "")

  if (isInNet (resolved_ip, "172.17.0.0", "255.255.0.0"))

   retStr = proxy_no;

if (retStr == "")

  if (isInNet (resolved_ip, "172.18.0.0", "255.255.0.0"))

   retStr = proxy_no;

if (retStr == "")

  if (isInNet (resolved_ip, "172.19.0.0", "255.255.0.0"))

   retStr = proxy_no;

if (retStr == "")

  if (isInNet (resolved_ip, "172.20.0.0", "255.255.0.0"))

   retStr = proxy_no;

if (retStr == "")

  if (isInNet (resolved_ip, "192.168.0.0", "255.255.0.0"))

   retStr = proxy_no;

if (retStr == "")

  if (isInNet (resolved_ip, "10.0.0.0", "255.0.0.0"))

   retStr = proxy_no;

// default to use proxy

if (retStr == "")

         retStr = proxy_yes;

return retStr;

    }

Hope this helps to find the root cause of this issue.

Regards,

Ulrich