https://bz.apache.org/bugzilla/show_bug.cgi?id=66969
Bug ID: 66969
Summary: After a timeout, mod_proxy_http2 doesn't initiate a
new connection immediatly
Product: Apache httpd-2
Version: 2.4.57
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: mod_proxy_http2
Assignee: bugs@httpd.apache.org
Reporter: martin.bl...@bpm.ch
Target Milestone: ---
We get some 503 errors with mod_proxy_http2 and H2-proxypass after some timeout
period. The problem only appears after the timeout. Instead of initiating a new
connection, the apache proxy is answering with a 503 error after the timeout
period.
The problem appears in a webshop after 300 seconds of inactivity. After the
timeout period the next request (doesn't matter which if html or other files)
fails with an 503 error and we can't ourselves point the customer to the logout
page (after the internal shop timeout). So the 503 error is ugly and for
production webservers a blocker.
This is the main part of the apache config, which leads to problems:
SSLEngine on
SSLProxyEngine On
SSLProxyCheckPeerCN off
SSLProxyCheckPeerExpire off
SSLProxyCheckPeerName off
ProxyPreserveHost On
ProxyRequests Off
ProxyPass / h2://xxxweb.customer/
ProxyTimeout 650
Sidenote: The same config with mod_proxy_http and HTTP/1.1 SSL works perfect
even after the timeout period:
SSLEngine on
SSLProxyEngine On
SSLProxyCheckPeerCN off
SSLProxyCheckPeerExpire off
SSLProxyCheckPeerName off
ProxyRequests Off
ProxyPreserveHost On
ProxyPass / https://xxxweb.customer/
ProxyTimeout 650
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
