I tried adding the line UseCanonicalPhysicalPort off to both
apache2.conf and to the site configuration (inside the virtualhost
declaration), but the port is still included in the Location header.
Just to be sure, I also tried UseCanonicalName off, but it didn't make
any difference.
--
You
Are you sure you have the same configuration for all versions? The
behavior is defined by UseCanonicalName and UseCanonicalPhysicalPort:
http://httpd.apache.org/docs/2.2/mod/core.html#usecanonicalphysicalport
The behavior you describe for 2.2.22-1ubuntu1 seems to match the one for
It looks like this has been fixed in a later version of Apache -- I've
just compiled 2.4.2 from source and it doesn't appear to have the
problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is this really a bug, or a new feature in a future Apache version?
Traditionally, Apache used to issue redirects based on its own knowledge
of its own name (and presumably port), rather than using the Host
Is this really a bug, or a new feature in a future Apache version?
Traditionally, Apache used to issue redirects based on its own knowledge of
its own name (and presumably port), rather than using the Host header, didn't
it?
If that's the case, then surely Apache should ignore the Host
Apache has to use the Host header to match a virtual entry. But you may
well be right - I'm no authority on this.
I think that to progress with triage of this bug, we need to determine
if the latest 2.2 upstream is affected. If it is not, then a backported
fix may be justified, so the next step
Marking as Incomplete for now, since to verify if the bug is valid, I
think we need confirmation from upstream - either that their latest 2.2
release built from source does not have the problem, or in the form of a
commit in the 2.2 series where they fixed it, or in their acceptance of
a bug, or
I've just compiled httpd 2.2.22 from source, and it does not appear to
have this bug.
** Changed in: apache2 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
