[Bug 1018285] Re: Redirects incorrectly set Location header in response when Host header is set in request

[Michael Williamson]

> 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 header
entirely, rather than using the hostname from the Host header, and the
port Apache is running on? The fact that it works correctly when the
port is explicitly set in the Host header makes me pretty sure this is a
bug -- when the port in the Host header isn't explicitly set, it should
mean there's an implicit port i.e. port 80 for HTTP, so the behaviour
should be consistent whether the port is explicit or implicit in the
Host header.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1018285

Title:
  Redirects incorrectly set Location header in response when Host header
  is set in request

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1018285/+subscriptions