Summary: | please clarify "default port" in UseCanonicalPhysicalPort documentation | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Christoph Anton Mitterer <calestyo> |
Component: | Documentation | Assignee: | HTTP Server Documentation List <docs> |
Status: | NEW --- | ||
Severity: | minor | ||
Priority: | P2 | ||
Version: | 2.5-HEAD | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Christoph Anton Mitterer
2021-01-21 05:46:33 UTC
Oh and perhaps please clarify the following in addition: Is there any risk or other drawback in using the non-default UseCanonicalPhysicalPort On I just wondered that the default is Off, cause to me it seemed like the more "natural" behaviour if Apache would use the physical port (actually even over the "Port provided in Servername" respectively "Parsed port from Host: header")... cause this is the port where it's already clear that the client "successfully" ended up at the vhost that also sends the redirect (which likely goes into the vhost again - when we speak of things like error documents or mod_dir /-addition). And one more: It seems at least in the UseCanonicalName On (but probably also for off) AND UseCanonicalPhysicalPort On case: The two lines "Port provided in Servername" in the order list of the doc really mean "the LITERALLY provided port number, if any". That is if one says: a) ServerName example.org => the rule *won't* kick in, and e.g. the physical port kicks in but: b) ServerName example.org:80 (i.e. the :80 literally written in the config, and not just the silent "default" => the rule *does* kick in, and e.g. the physical port is ignored |