listen for haproxy on different port about velocity

[clrxbl]

This realistically should be #1046
An alternative workaround for now would be to host a secondary Velocity instance with HAProxy enabled.

[shithubsucks]

I feel like the scope on #1046 is a bit different but thank you for the workaround suggestion. That should work in the meantime but is massively inefficent. There is some crossover however, as I believe the issue in #1046 could possibly be addresses with the addition of haproxy and it's ability to arbitrarily bind to anything it's host can. The primary purpose of this is to preserve the source ip address to the application servers.

[shithubsucks]

The workaround of running a second velocity daemon seemed to have worked. I appreciate it. This is hardly ideal though.

[electronicboy]

The scope is the exact same, just with the caveat that you also want haproxy to be configurable per listener; closing as a duplicate of #1046