While playing around with perlbal I've got it running on a nonstandard
port. I found that since the Host header contains a port number the
vhost module fails to match to the right vhost.

I think the easiest fix is just to strip the port off completely, and
the simple patch I've attached does that very thing. There seems little
point in using the client-supplied port number when there's a real port
number available on the socket itself.

[ Post a follow-up to this message ]

Go ahead and check it in with a Changelog update.  Also \d is probably
better than . for after the colon.


On Wed, 17 Aug 2005, Martin Atkins wrote:

> While playing around with perlbal I've got it running on a nonstandard
> port. I found that since the Host header contains a port number the
> vhost module fails to match to the right vhost.
>
> I think the easiest fix is just to strip the port off completely, and
> the simple patch I've attached does that very thing. There seems little
> point in using the client-supplied port number when there's a real port
> number available on the socket itself.
>
>

[ Post a follow-up to this message ]