tux virtual host listening on non-standard port

I have run in to a problem using mass virtual hosting while having tux 
listen on a non-standard port.

On start up, I have been setting /proc/net/tux/0/listen/0 to 
"http://10.2.207.2:8082" and everything works fine there.  However, when 
I try to enable mass virtual hosting based on the host header 
("net.tux.virtual_server = 1") the virtual hosting does not work.  I 
assume that this is because the host header in the request reads "Host: 
name.of.host:8082" rather than "Host: name.of.host" and so tux cannot 
find the content it is supposed to serve.  I even tried creating an 
additional symbolic link pointing name.of.host:8082 --> name.of.host in 
my document root, but it doesn't appear to make a difference.

I have worked around this by moving my tux listener back to port 80, but 
I thought I would bring this up as I would love to understand if this is 
a bug or if I am missing something.

cb