You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2020/02/27 02:45:03 UTC

[Bug 64181] New: UseCanonicalPhysicalPort

https://bz.apache.org/bugzilla/show_bug.cgi?id=64181

            Bug ID: 64181
           Summary: UseCanonicalPhysicalPort
           Product: Apache httpd-2
           Version: 2.4.29
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
          Assignee: bugs@httpd.apache.org
          Reporter: wellmanadmin@gmail.com
  Target Milestone: ---

Hello,

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/
</VirtualHost>


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

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org