httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 50551] Some proxied connections ignore ttl setting
Date Fri, 01 Apr 2011 14:00:21 GMT

--- Comment #5 from Slawo <> 2011-04-01 10:00:19 EDT ---
Hi everybody,
I have now been able to track down the reason for the bug.
The problem is that we are using the prefork model Apache.
If I use the worker model, the problem is gone.

I have analyzed the source of the mod_proxy module and found this inside

/* Connection pool */
struct proxy_conn_pool {
    apr_pool_t     *pool;   /* The pool used in constructor and destructor
calls */
    apr_sockaddr_t *addr;   /* Preparsed remote address info */
    apr_reslist_t  *res;    /* Connection resource list */
    proxy_conn_rec *conn;   /* Single connection for prefork mpm's */

Apparently, when using the prefork model, the ttl and smax setting are not
applied to the *conn entry.

I don't know if this is possible at all, but is there a reason that this
connection doesn't expire?

In fact, what we really need is not an option for expiry of the connections
after idle timeout. We would rather very like to have an option to refresh the
IP-address of the connections in case the DNS resolver delivers a different

There is such an option in the mod_weblogic module for Weblogic. It's named
WLDNSRefreshInterval and would be very useful in the mod_proxy module, too.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message