At master (including back at 1316237 following the port convention changes without 0.9.5 re-merging) the behavior of the global/base server for a ServerName sans-port number results in;
Default port 80 or 443 or any other protocol-specific default port would be implied;
ServerName example.com
bmx-handler output:
Name: mod_bmx_vhost:Type=forever,Host=example.com,Port=_ANY_
To qualify the Port as something other-than _ANY_, one needs to dig into the protocol itself, whether SSLEngine on was specified, or another protocol altogether is in-force.
If the ServerName is port decorated as example.com:80 - the bmx-handler result is:
Name: mod_bmx_vhost:Type=forever,Host=example.com,Port=80
This seems to be an appropriate behavior; but leaving this open for discussion.
At master (including back at 1316237 following the port convention changes without 0.9.5 re-merging) the behavior of the global/base server for a ServerName sans-port number results in;
Default port 80 or 443 or any other protocol-specific default port would be implied;
ServerName example.com
bmx-handler output:
Name: mod_bmx_vhost:Type=forever,Host=example.com,Port=_ANY_To qualify the Port as something other-than
_ANY_, one needs to dig into the protocol itself, whether SSLEngine on was specified, or another protocol altogether is in-force.If the ServerName is port decorated as example.com:80 - the bmx-handler result is:
Name: mod_bmx_vhost:Type=forever,Host=example.com,Port=80This seems to be an appropriate behavior; but leaving this open for discussion.