https://bz.apache.org/bugzilla/show_bug.cgi?id=65617
Bug ID: 65617
Summary: Infinite redirect loop with new mod_proxy changes
Product: Apache httpd-2
Version: 2.4.49
Hardware: PC
OS: Linux
Status: NEW
Severity: regression
Priority: P2
Component: mod_proxy_http
Assignee: bugs@httpd.apache.org
Reporter: ca...@alerque.com
Target Milestone: ---
I just updated a production server from 2.4.48 to 2.4.49 and the Apache daemon
started crashing a few minutes later. First the process list would max out as
as many workers as it was allowed to run (mpm_prefork), then the memory use
would gradually go up. With all the threads busy, new requests started timing
out.
I traced the issue to a redirect to a unix socket that was setup like this:
RewriteRule .* unix:/path/to.socket|http://example.com%{REQUEST_URI}
[P,QSA,NE]
This was resolving to an infinite loop of redirects. The log files were quickly
filling up with ever-longer redirect chains. This syntax worked perfectly until
2.4.49.
I was able to get something up temporarily by switching to:
ProxyPass / "unix:///path/to.socket|http://example.com/";
But this is unsatisfactory as it does not allow me to catch and handle various
other rewrites in the same context as the ones being proxied. I fussed and
fidgeted and could not come up with a syntax for using RewirteRule to proxy to
a socket that does not generate infinite loops.
The changelog for 2.4.49 mentions several issues (PR 65521 and 65519, "Faster
unix socket path parsing", and others. Of course all of these sound like fixes
for problems, but one of them seems to have caused a regression.
--
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
