Issue about ServerName

[Paul B. Henson]

On 10/30/2024 5:37 PM, Konoma via users wrote:

> Due to business requirements, the following ServerName must be set in httpd.conf:
> ServerName inst01:8091

This directive tells the server what its *external* identity is, not the 
internal details of which port/protocol it is actually listening on.

With this configuration, the server identifies itself as 
"http://inst01:8091/", which obviously doesn't match 
"https://test.example.com/".

Unsurprisingly, when you give the server the correct information as to 
its external identity, it works.

What exactly is the "business requirement" to configure the server such 
that its understanding of the externally presented URL does not match 
reality? If you want the server to live and function properly behind a 
proxy (in this case an SSL terminating load balancer), it has to know 
what URL the end-user browser supplied to that proxy.