#4459: libpurple should use libproxy
-----------------------------+----------------------------------------------
Reporter: kipple | Owner:
Type: enhancement | Status: new
Milestone: Patches welcome | Component: libpurple
Version: 2.3.1 | Resolution:
Keywords: |
-----------------------------+----------------------------------------------
Comment(by felipec):
Replying to [comment:2 rekkanoryo]:
> Note that libproxy is wildly deficient currently; this has been
discussed at least twice. It is missing at least the ability to determine
the type of proxy.
Care to mention what is missing?
If you read *any* libproxy documentation you would find:
* The format of the returned proxy strings are as follows:
* - http://[username:password@]proxy:port
* - socks://[username:password@]proxy:port
* - socks5://[username:password@]proxy:port
* - socks4://[username:password@]proxy:port
* - <procotol>://[username:password@]proxy:port
* - direct://
--
Ticket URL: <http://developer.pidgin.im/ticket/4459#comment:4>
Pidgin <http://pidgin.im>
Pidgin