Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global (base) server reports #4

Open
wrowe opened this issue Nov 9, 2015 · 0 comments
Open

Global (base) server reports #4

wrowe opened this issue Nov 9, 2015 · 0 comments
Assignees

Comments

@wrowe
Copy link
Contributor

wrowe commented Nov 9, 2015

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.

@wrowe wrowe self-assigned this Nov 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant