httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 61855] Using mod_rewrite and mod_proxy does not allow for backend keep-alive
Date Tue, 26 Dec 2017 19:24:16 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=61855

Eric Covener <covener@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #2 from Eric Covener <covener@gmail.com> ---
(In reply to Dave Mulford from comment #0)
> When using mod_rewrite and mod_proxy together to create a reverse proxy
> based on the Host http header, connection reuse is disabled.
> 
> Here is a sample configuration:
> 
> --- SAMPLE CONFIG ---
> RewriteEngine On
> RewriteRule .* - [E=TARGET:%{HTTP_HOST}]
> 
> SSLProxyEngine on
> SSLProxyCheckPeerName off
> SSLProxyCheckPeerCN off
> SSLProxyCACertificatePath /etc/certs/
> SSLProxyVerify none
> 
> ProxyPass / https://${TARGET}/ retry=0 ttl=5 keepalive=on interpolate
> ProxyPassReverse / https://${RARGET}/ interpolate
> ProxyPassInterpolateEnv on
> ProxyPreserveHost On
> --- END SAMPLE CONFIG ---

For reuse, the server needs to know the backend workers in advance.  TARGET is
not known until request processing.  You need to list out the backends you want
a dedicated worker for.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Mime
View raw message