Then in 2.2, presence of UseCanonicalPhysicalPort, should remove optional
port argument of ServerName.
As it behaves unexpectedly.
Thanx
- Original Message -
From: Sander Temme
To: users@httpd.apache.org
Date: Tue, 14 Jul 2009 15:33:19 -0700
Subject: Re: [us...@httpd] Canonical
On Jul 14, 2009, at 3:24 PM, Marcin 'Rambo' Roguski wrote:
SERVER_PORT gets value from ServerName no matter what value of
UseCanonicalName is
Workaround is to not set a port in ServerName
Is this a bug?
You're missing Port directive.
Port is no longer in httpd 2.x. But try to play with
> SERVER_PORT gets value from ServerName no matter what value of
> UseCanonicalName is
> Workaround is to not set a port in ServerName
>
>
> Is this a bug?
You're missing Port directive.
-
The official User-To-User support for
UseCanonicalName On
ServerName LIMPETstarforce.biz:69
---
Result:
SERVER_NAME = LIMPETstarforce.biz
SERVER_PORT = 69
UseCanonicalName Off
ServerName LIMPETstarforce.biz:69
---
Result
