DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43756>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43756

           Summary: Can't set retry=0 in mod_proxy
           Product: Apache httpd-2
           Version: 2.2.6
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Documentation
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Hello, 

i have found a little error in mod_proxy.c, it is not possible to set retry=0.

----------
Documentation (http://httpd.apache.org/docs/2.2/mod/mod_proxy.html):
retry   60      Connection pool worker retry timeout in seconds. If the 
connection
pool worker to the backend server is in the error state, Apache will not forward
any requests to that server until the timeout expires. This enables to shut down
the backend server for maintenance, and bring it back online later. A value of 0
means always retry workers in an error state with no timeout.
---------
mod_proxy.c :
    else if (!strcasecmp(key, "retry")) {
        /* If set it will give the retry timeout for the worker
         * The default value is 60 seconds, meaning that if
         * in error state, it will be retried after that timeout.
         */
        ival = atoi(val);
        if (ival < 1)    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
            return "Retry must be at least one second";
        worker->retry = apr_time_from_sec(ival);
----------

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to