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

2012-07-04 Thread Michael Williamson
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 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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2012-06-29 Thread Stefan Fritsch
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
UseCanonicalPhysicalPort on while the compiled from source behavior
seems to correspond to off

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2012-06-27 Thread Michael Williamson
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.
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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2012-06-27 Thread Robie Basak
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
header, didn't it? I'm pretty sure that it used to be the case that it
was essential for Apache to know its own name correctly for this reason.

I wonder if upstream considers this a bug? Have they fixed it in the 2.2
series?

** Changed in: apache2 (Ubuntu)
   Importance: Undecided = Medium

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2012-06-27 Thread 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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2012-06-27 Thread Robie Basak
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 would be to identify the upstream
2.2 series commit that fixed this issue. If the latest 2.2 upstream is
not affected, then upstream would be the appropriate place to seek
guidance from, perhaps by filing a bug there.

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2012-06-27 Thread Robie Basak
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 some other form of confirmation. I don't think it's
appropriate to seek a fix solely for Ubuntu otherwise. If the situation
changes, please comment and change the bug status back to New.

** Changed in: apache2 (Ubuntu)
   Status: New = Incomplete

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2012-06-27 Thread Michael Williamson
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.
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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs