Tk Library Source Code

autoproxy::init (version 1.2.0) fails under WinXP Pro 
when the following line of code:

registry get $winregkey "ProxyServer"

returns a value like:

ftp=quantex:8080;gopher=quantex:8080;http=quantex:8
080;https=quantex:8080

instead of a value like:

quantex:8080

This happens whenever "Control Panel | Internet 
Options | Connections | LAN
Settings | Advanced" | "Use the same proxy server for all
protocols" *is not* checked, and instead, each protocol 
is defined independently.

The attached autoproxy.tcl has been patched to fix the 
problem for my case, though I don't know enough about 
this domain to be confident that the patch is generally 
safe.  Specifically...

1. Is it safe to parse this key (in the general case) using 
[split]?
2. Is the key always semi-colon separated?
3. Am I always after the "http" portion of the key?

Jeff

Logged In: YES 
user_id=202636

Added support for this to the autoproxy package. At this
time we do not have sufficient information to differentiate
between https and http at the point where we hook into the
http package - therefore we always use the http proxy setting.

The http package should be enhanced to support this -- but
then the http package needs many enhancements and a general
support for proxies is one part of that.

Logged In: YES 
user_id=202636

http://support.microsoft.com/?id=819961 suggests it will be
of the form http://servername:port/
Elsewhere MS documentation says "ProxyServer – This entry
specifies the URL and port number for the proxy server."

However, if you fill in different servers for each proxy
type in the Internet explorer settings you indeed get the
above string. This is with IE6. Probably the same for other
versions.

I think it is safe to split the string using ; and we will
want the proxy for the protocol desired - that may be http
or https for autoproxy purposes.

File Added - 115183: autoproxy.tcl