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=44051>. 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=44051 Summary: Add source to "The timeout specified has expired" log message Product: Apache httpd-2 Version: 2.3-HEAD Platform: All OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Core AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] If possible, enhance a message such as: [Mon Dec 10 22:37:26 2007] [error] [client 10.10.10.1] (70007)The timeout specified has expired: proxy: error reading status line from remote server localhost to indicate the configuration directive in effect for determining the Timeout. This would make it easier for an admin to fix a problem. Scenario: I had a backend behind a reverse proxy timing out no matter how high I set the ProxyTimeout value. Finally I realized the Timeout value in the base configuration was taking precedence (I think the patch on bug 11540 changes this to the behavior I was expecting) and once I knew that the fix was trivial. If the error message had read: (70007)The timeout specified by the Timeout parameter has expired: proxy: error reading status line from remote server localhost that would have been more helpful. I make this request not knowing if there's a generalized mechanism for marshaling this data around, of course. Looking at the SVN for bug 11540 I can see there are at least three cases for just the proxy case, probably others I'm not aware of. -- 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]
