Yabi-be Backend port settings acting in unexpected way

[GoogleCodeExporter]

yabi.conf backend section:

port: 192.168.1.96:9001
netstat:

tcp        0      0 0.0.0.0:9001                0.0.0.0:*                   
LISTEN 

The ip address part of this doesn't appear to actually cause it to bind to only 
that IP address, but it does affect what the backend identifies itself as to 
admin (origin):

192.168.1.96 - - [07/Oct/2010:16:19:15 +0800] "GET 
/yabiadmin/engine/task/?origin=192.168.1.96:9001 HTTP/1.0" 404 17 "-" 
"YabiExec/0.1"

Once you are aware of this it works correctly, the configuration directive is 
just misleading.

Original issue reported on code.google.com by ahunter.ccg@gmail.com on 6 Jul 2011 at 9:01

[GoogleCodeExporter]

Original comment by aahun...@gmail.com on 29 Jul 2011 at 3:00

• Changed title: Yabi-be Backend port settings acting in unexpected way

[GoogleCodeExporter]

Original comment by aahun...@gmail.com on 29 Jul 2011 at 3:32

• Added labels: Priority-High, Milestone-Pending
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by retrogra...@gmail.com on 2 Aug 2011 at 2:37

[GoogleCodeExporter]

fixed in rev: 764514f8b4e0

Original comment by retrogra...@gmail.com on 2 Aug 2011 at 3:24

• Changed state: Fixed