- Timestamp:
- 2015-08-28T02:05:45Z (9 years ago)
- Branches:
- master
- Children:
- f5bbaba
- Parents:
- b6a3fbf
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
rb6a3fbf raa3b61e 1324 1324 </bitlbee-setting> 1325 1325 1326 <bitlbee-setting name="proxy" type="string" scope="account"> 1327 <default><local><auto></default> 1328 1329 <description> 1330 <para> 1331 A list of <emphasis>file transfer proxies</emphasis> for jabber. This isn't the connection proxy. Sorry, look in bitlbee.conf for those. 1332 </para> 1333 1334 <para> 1335 It's a semicolon-separated list of items that can be either <emphasis>JID,HOST,PORT</emphasis> or two special values, <emphasis><local></emphasis> (to try a direct connection first) and <emphasis><auto></emphasis> (to try to discover a proxy). For example, "<local>;proxy.somewhere.org,123.123.123.123,7777". 1336 </para> 1337 <para> 1338 The address should point to a SOCKS5 bytestreams server, usually provided by jabber servers. This is only used for sending files. Note that the host address might not match what DNS tells you, and the port isn't always the same. 1339 </para> 1340 <para> 1341 The correct way to get a socks proxy host/port is a mystery, and the file transfer might fail anyway. Maybe just try using dropbox instead. 1342 </para> 1343 </description> 1344 </bitlbee-setting> 1345 1326 1346 <bitlbee-setting name="query_order" type="string" scope="global"> 1327 1347 <default>lifo</default>
Note: See TracChangeset
for help on using the changeset viewer.