This post is as a request as well as an fyi for a workaround.
Request: Please consider adding socks support for the proxy options.
Curl supports it just fine as --socks5 [proxy]:[port] instead of only allowing -x [proxy]:[port]
Workaround: If you've only got a socks proxy available to you to do updates with, you can squeeze your socks proxy string into the "Address" field by entering it as:
127.0.0.1 --socks5 127.0.0.1:8080
Once you save it, your apup.ini would look like:
[Proxy]
UseProxy=1
Address=127.0.0.1 --socks5 127.0.0.1:8080
Port=8080
UseAuthentication=0
[General]
RememberSelections=0
The Port= port is not used for the socks part, it can be anything.
What this does is passes the proxy info to curl in the following format:
curl -x 127.0.0.1:8080 --socks5 127.0.0.1:8080
So it passes BOTH options, and thereby allows you to use a socks proxy to download updates if you do not have or want to use a http proxy.
Love the product all. Continually great job, always impressed.
-srsalt
1 reply to this topic
#1
Posted 10 October 2011 - 11:38 PM
#2
Posted 11 October 2011 - 03:35 AM
Good info for users of current apup.
The current code in apup2 supports socks and html proxy. Although that may change as im thinking of using a different way to download using windows api.
There are also programs that can capture an individual programs internet connections and route them to a sock server. I just don't remember what they are called atm.
The current code in apup2 supports socks and html proxy. Although that may change as im thinking of using a different way to download using windows api.
There are also programs that can capture an individual programs internet connections and route them to a sock server. I just don't remember what they are called atm.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











