Bug 64181 - UseCanonicalPhysicalPort
Summary: UseCanonicalPhysicalPort
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.4.29
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Depends on:
Reported: 2020-02-27 02:45 UTC by mark
Modified: 2020-02-27 02:45 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description mark 2020-02-27 02:45:03 UTC

I use haproxy to wrap multiple back end hosts with ssl for easy ssl updates. Apache2 virtual hosts seem to be responding with the server port specified in the VirtualHost directive, regardless of UseCanonicalName/UseCanonicalPhysicalPort and the FQDN specified in the Servername directive. This issue seems similar to 63504; however, I cannot use the "work around" specified by setting the ServerName with the default port, as it should set SERVER_PORT.

<VirtualHost *:8085>
	SSLEngine On
	SSLCertificateFile <example>
	SSLCertificateKeyFile <example>
	UseCanonicalName on
	UseCanonicalPhysicalPort on
        ServerName https://example1.example2:443
        DocumentRoot /var/www/wordpress/

Browser redirects to https://example1.example2:8085 regardless of values specified for either UseCanonicalName or UseCanonicalPhysicalPort.