To configure the proxy server for Zionworx depends upon the code base that the developers have used to do HTTP connections - I am not one of the developers, so I do not know which (if any) of these will work.
If WinInet is used then you configure your proxy via Internet Explorer or the Control Panel. These settings are set in Internet Explorer > Tools > Connections dialog. Click LAN Settings button and enter your proxy server details, ensuring that
http://www.biblegateway.com is not on the exceptions list (or indeed that something like *.com etc. is not excepted, as that would include Bible Gateway).
The WinInet HTTP interface uses Internet Explorer code to reach the internet, and is usually used on client applications (such as Zionworx). But the alternative for better performance (and therefore typically used on server applications that need HTTP access is WinHTTP). If WinHTTP is used then you need to set the WinHTTP proxy settings and see if that makes a difference. This can be set using proxycfg, which is available if you have installed some WinHTTP development tools. See
http://support.microsoft.com/kb/289481 for more
- Code: Select all
proxycfg -p proxy_server "<local>"
The above command specifies that both HTTP and HTTPS servers are accessed through the proxy server named "proxy_server", except for host names that do not contain a period. See
http://msdn.microsoft.com/en-us/library/aa384069(VS.85).aspx for more command line options and how to specific specific ports.
If WinInet or WinHTTP are not used then we need to wait to hear from the developers as to what HTTP connection library they use and how to configure a proxy for it, hoping for you that the only way to do this is not inside the application - or you will need to make a post on the wish list forum.