Ubuntu
apache2 package

Missing Reason-Phrase in HTTP response header for *standard* 3-digit status codes

Bug #1265530 reported by Jarl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Apache2 Web Server
Unknown
Unknown
apache2 (Ubuntu)
Fix Released
Medium
Unassigned
Saucy
Won't Fix
Medium
Unassigned
Trusty
Fix Released
Medium
Unassigned

Bug Description

Upgrading to 13.10 introduced this bug, it is very well documented on

https://issues.apache.org/bugzilla/show_bug.cgi?id=54946

Revision history for this message
Robie Basak (racb) wrote :

Thank you for reporting this bug and helping to make Ubuntu better.

AFAICT, this should have been fixed in 2.4.7, which has just been uploaded to Debian today. So this should be fixed in Trusty on the next merge, and we should definitely do this in time for Trusty's release.

Please could someone explain the impact to users on 13.10 so that we can decide if we need to backport this fix to Saucy in a stable release update? Rationale at: https://wiki.ubuntu.com/StableReleaseUpdates

Changed in apache2 (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Jarl (jarl-dk) wrote :

I don't think any end-users are seriously affected (not even developers using apache).

Howeverenterprise installations seems to be the ones that are affected:
The reporter discovered the problem in combination with Phusion passenger (Ruby on Rails stack), that is also the case for me and another commenter on the apache bug.

I ran into this problem when I upgraded hosts that nagios is watching. Nagios starting to report problems because of this.

Another commenter on the apache bug ran into this problem when the http server was behind a varnish installation, apparently varnish also rely on this to work.

So it seems mostly to be a problem in an Enterprise server setup, but that is also bad enough I think...

Jarl

Robie Basak (racb)
Changed in apache2 (Ubuntu Saucy):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Robie Basak (racb) wrote :

I've uploaded apache2 2.4.7-1ubuntu1. As https://issues.apache.org/bugzilla/show_bug.cgi?id=54946#c14 suggests that this was fixed in upstream 2.4.7, I'm marking this as Fix Released. If this is incorrect, please explain and reopen.

For Saucy, I looked at reproducing the issue for a test case, but then realised that the bug doesn't trigger with straightforward static file serving. Since I don't have exact steps to reproduce to write a test case, I can't proceed with an SRU. I also need an SRU justification filled out. So I'm marking this as Incomplete in Saucy. If anybody wants to drive through a fix to Saucy, please follow the steps at: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Changed in apache2 (Ubuntu Saucy):
status: Triaged → Incomplete
Changed in apache2 (Ubuntu Trusty):
status: Triaged → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

saucy has seen the end of its life and is no longer receiving any updates. Marking the saucy task for this ticket as "Won't Fix".

Changed in apache2 (Ubuntu Saucy):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.