[Bug 1495988] Re: ProxyErrorOverride leads to slow 404 responses
ChristianEhrhardt
1495988 at bugs.launchpad.net
Mon Jun 27 09:09:05 UTC 2016
FYI - The other bug is now cleared, also I prepared a simplified test that I'll add now to the SRU description.
Could this be reevaluated for upload to proposed?
** Description changed:
[Impact]
- * hang until ProxyTimeout timeout if ProxyErrorOverride is set
- * see https://bz.apache.org/bugzilla/show_bug.cgi?id=53420 for more
+ * hang until ProxyTimeout timeout if ProxyErrorOverride is set
+ * see https://bz.apache.org/bugzilla/show_bug.cgi?id=53420 for more
[Test Case]
- * use the feature of https://httpd.apache.org/docs/current/mod/mod_proxy.html#proxyerroroverride
+ 1. spawn 2x trusty container
+ 2. install apache2 on both
+ 3. Mark /var/www/html/index.html to verify frontend/backend setup
+ 4. enable mod_proxy and ProxyErrorOverride Directive
+ ln -s ln -s /etc/apache2/mods-available/xml2enc.load /etc/apache2/mods-enabled/
+ ln -s /etc/apache2/mods-available/proxy* /etc/apache2/mods-enabled/
+ rm /etc/apache2/mods-enabled/proxy_balancer.*
+ On Frontend in /etc/apache2/mods-enabled/proxy.conf add (IP is backend)
+ ProxyPass "/proxme" "http://10.0.4.44/"
+ ProxyPassReverse "/proxme" "http://10.0.4.44/"
+ ProxyErrorOverride On
+ ProxyTimeout 5
+ 5. verify that:
+ on http:/Frontend/proxme you get the backend index.html page
+ local and remote pages still work fine
+ local errors are still fast
+ proxied errors are slowed by ProxyTimeout (5 sec)
+ time wget http://10.0.4.95/proxme/index-notthere.html
+ real 0m4.987s
+ proxied errors are slow now
+ time wget http://10.0.4.95/proxme/index-notthere.html
+ real 0m4.987s
+ ab -n 100 -c 100 http://10.0.4.95/proxme/index-notthere.html
+ Total: 4931 5186 433.9 4934 5936
+ 6. On Frontend enable proposed, update and restart apache2
+ 7. Verify things are now fast
+ time wget http://10.0.4.95/proxme/index-notthere.html
+ ab -n 100 -c 100 http://10.0.4.95/proxme/index-notthere.html
[Regression Potential]
- * the patch is small and already backported by Apache people which is good
- * The changes are local to mod_proxy only which should limit the potential fallout
- * all basic tests I did still work, but we have to rely on a real test by the reporter from proposed for the actual Test
+ * the patch is small and already backported by Apache people which is good
+ * The changes are local to mod_proxy only which should limit the potential fallout
+ * all basic tests I did still work, but we have to rely on a real test by the reporter from proposed for the actual Test
[Original Description]
Like described in #53420 [1] there is a bug in Apache 2.4.x which is
fixed in 2.4.11.
This bug leads to slow 404 responses when ProxyErrorOverride is
activated.
--------------------
When setting ProxyErrorOverride to "On" to get the httpd-ErrorDocument
instead of the backend-errordoc, httpd is waiting "ProxyTimeout" seconds
to respond to the client, even though the response is already read from
backend server.
--------------------
The bug is fixed in 2.4.11 [2]. Is there any chance to get this fix into
the Ubuntu package for 14.04 LTS?
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=53420
[2] https://svn.apache.org/viewvc?view=revision&revision=1621601
-----------
$ apt-cache policy apache2
apache2:
Installed: 2.4.7-1ubuntu4.5
Candidate: 2.4.7-1ubuntu4.5
Version table:
*** 2.4.7-1ubuntu4.5 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
100 /var/lib/dpkg/status
2.4.7-1ubuntu4 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
-----------
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1495988
Title:
ProxyErrorOverride leads to slow 404 responses
Status in Apache2 Web Server:
Fix Released
Status in apache2 package in Ubuntu:
Fix Released
Status in apache2 source package in Trusty:
Triaged
Bug description:
[Impact]
* hang until ProxyTimeout timeout if ProxyErrorOverride is set
* see https://bz.apache.org/bugzilla/show_bug.cgi?id=53420 for more
[Test Case]
1. spawn 2x trusty container
2. install apache2 on both
3. Mark /var/www/html/index.html to verify frontend/backend setup
4. enable mod_proxy and ProxyErrorOverride Directive
ln -s ln -s /etc/apache2/mods-available/xml2enc.load /etc/apache2/mods-enabled/
ln -s /etc/apache2/mods-available/proxy* /etc/apache2/mods-enabled/
rm /etc/apache2/mods-enabled/proxy_balancer.*
On Frontend in /etc/apache2/mods-enabled/proxy.conf add (IP is backend)
ProxyPass "/proxme" "http://10.0.4.44/"
ProxyPassReverse "/proxme" "http://10.0.4.44/"
ProxyErrorOverride On
ProxyTimeout 5
5. verify that:
on http:/Frontend/proxme you get the backend index.html page
local and remote pages still work fine
local errors are still fast
proxied errors are slowed by ProxyTimeout (5 sec)
time wget http://10.0.4.95/proxme/index-notthere.html
real 0m4.987s
proxied errors are slow now
time wget http://10.0.4.95/proxme/index-notthere.html
real 0m4.987s
ab -n 100 -c 100 http://10.0.4.95/proxme/index-notthere.html
Total: 4931 5186 433.9 4934 5936
6. On Frontend enable proposed, update and restart apache2
7. Verify things are now fast
time wget http://10.0.4.95/proxme/index-notthere.html
ab -n 100 -c 100 http://10.0.4.95/proxme/index-notthere.html
[Regression Potential]
* the patch is small and already backported by Apache people which is good
* The changes are local to mod_proxy only which should limit the potential fallout
* all basic tests I did still work, but we have to rely on a real test by the reporter from proposed for the actual Test
[Original Description]
Like described in #53420 [1] there is a bug in Apache 2.4.x which is
fixed in 2.4.11.
This bug leads to slow 404 responses when ProxyErrorOverride is
activated.
--------------------
When setting ProxyErrorOverride to "On" to get the httpd-ErrorDocument
instead of the backend-errordoc, httpd is waiting "ProxyTimeout" seconds
to respond to the client, even though the response is already read from
backend server.
--------------------
The bug is fixed in 2.4.11 [2]. Is there any chance to get this fix
into the Ubuntu package for 14.04 LTS?
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=53420
[2] https://svn.apache.org/viewvc?view=revision&revision=1621601
-----------
$ apt-cache policy apache2
apache2:
Installed: 2.4.7-1ubuntu4.5
Candidate: 2.4.7-1ubuntu4.5
Version table:
*** 2.4.7-1ubuntu4.5 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
100 /var/lib/dpkg/status
2.4.7-1ubuntu4 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
-----------
To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1495988/+subscriptions
More information about the Ubuntu-sponsors
mailing list