https://issues.apache.org/bugzilla/show_bug.cgi?id=50551
Summary: Some proxied connections ignore ttl setting
Product: Apache httpd-2
Version: 2.3-HEAD
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy
AssignedTo: [email protected]
ReportedBy: [email protected]
In the solution for bug #43371 a patch was provided to enable setting of
smax=0.
Setting smax=0 ttl=30 doesn't seem to lead to dropping of the last connection,
though.
My expectation would be, that if I set smax to 0 then each connection should be
dropped after ttl expires.
Ways to reproduce:
1. Define a ProxyPass, e.g. like this:
NameVirtualHost 192.168.100.10:443
<VirtualHost 192.168.100.10:443>
SSLEngine ON
SSLProxyEngine ON
ProxyPass / https://backend.mydomain.com:8080/ disablereuse=On
ProxyPassReverse / https://backend.mydomain.com:8080/
</VirtualHost>
2. After making some requests to the proxy, change the ip-address of the server
backend.mydomain.com
3. When you now make a new request, the new ip-address of the backend will be
used.
4. Change the configuration to:
NameVirtualHost 192.168.100.10:443
<VirtualHost 192.168.100.10:443>
SSLEngine ON
SSLProxyEngine ON
ProxyPass / https://backend.mydomain.com:8080/ smax=0 ttl=30
ProxyPassReverse / https://backend.mydomain.com:8080/
</VirtualHost>
5. After making some requests change the ip-address of the server
backend.mydomain.com and wait for a time much bigger than ttl.
6. When you now make new requests, some of the requests, but not all(!) still
try to connect to the old ip-address of the backend.
Apparently not all connection have beed dropped after ttl expiry.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
