Bug 44051

Summary:	Add source to "The timeout specified has expired" log message
Product:	Apache httpd-2	Reporter:	Bill McGonigle <bill+apache>
Component:	Core	Assignee:	Apache HTTPD Bugs Mailing List <bugs>
Status:	RESOLVED FIXED
Severity:	enhancement
Priority:	P2
Version:	2.5-HEAD
Target Milestone:	---
Hardware:	All
OS:	other

Description Bill McGonigle 2007-12-10 21:01:50 UTC

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.

Comment 1 Eric Covener 2011-09-25 18:20:49 UTC

This is actually an old bug in ProxyTimeout, where the socket was being reset by the core Timeout.