Navigating corporate firewalls

No, there shouldn't be any issues with corporate firewalls. wyUpdate only uses HTTP and port 80 (allowed by almost every firewall in existence). Not only that, but wyUpdate tries to download files both using the proxy configuration on the computer, and if the download fails it tries again without using the proxy config.

This means wyUpdate is especially robust in downloading files.

If you have any more questions I'll be glad to answer them.

I've got a problem with a client running wyUpdate and trying to get through his proxy server/firewall at his office

In my program I allow the user to input their own username and password to get through a firewall, as well as allowing a custom proxy server in the configuration, which allows the administrator (It Guys) to disallow internet using a browser (no proxy), but allowing my program to connect out to the web, as well as giving the program it's own username and password for getting out to our site to get the updates.

Is it possible to add these to wyUpdate, as well as a mechanism of allowing the settings to be loaded into the program if wyUpdate is run as a seperate application.

I'm having problems getting some of my users updated because of this problem

ThanksDavid-John Miller

Does your client not allow his users to access the internet using their browsers? wyUpdate reads the proxy settings from Internet Explorer (and then tries again without proxy if the IE settings are misconfigured).

Have you tried setting the IE proxy settings using the WinHttpGetDefaultProxyConfiguration Function and WinHttpSetDefaultProxyConfiguration Function?

If you use WinHttpSetDefaultProxyConfiguration before running wyUpdate, then wyUpdate will use your custom proxy settings.

The client is not allowing the users to access the internet due to known abuse of the internet when it has been enabled, as well as knowing that the users would (and have) sat on the internet all day browsing instead of doing their actual work.

I will try the Set Default proxy option as well, but poses the same security risk as it would - i assume - allow internet explorer to function again, as well as not having any way to set the proxy back to defaults after the program has been updated.

This also doesn't fix allowing custom credentials - where the Admin would put authentication info into the program to get through their firewall with their username and password, which would allow the update to actually complete successfully

Ok, would a commandline switch like this work for you?

wyUpdate.exe /proxy:"http://proxyserver:80/"

If so I'll add it to wyUpdate.

That would be very useful, thanks

Also, if the proxy server asks for authentication, or authorization, can you make the updater ask for the credentials?(the proxy throws HTTP Error 407 Proxy authentication required)

Also, if the proxy server asks for authentication, or authorization, can you make the updater ask for the credentials?(the proxy throws HTTP Error 407 Proxy authentication required)

Actually, since you require password protected proxies, this solution would probably work better:

wyUpdate.exe /proxy:"http://proxyserver:80/" /proxyp:"PASSWORD" /proxyu:"USERNAME" /proxyd:"OPTIONAL_DOMAIN"

Would this work for you? Because prompting for a password is problematic. Namely, wyUpdate is used in "silent" mode when used with the AutomaticUpdater control. Thus, the dialog wouldn't pop up in such cases.

However if you are using the AutomaticUpdater control you can use the "wyUpdateCommandline". For example:

automaticUpdater.wyUpdateCommandline = "/proxy:\"http://proxyserver:80/\" etc....";

That will work perfectly

Next thing for me is getting my clients updated when the fix is in, and then for you is the wyInstall engine and all my program woes are fixed

Ok, wyBuild 2.5.13 is out. You can use the proxy switches on the new wyUpdate 2.5.13 like I describe above.