So that I know what customer of mine saw that error and I can pre-emptively respond to their dissatisfaction.
That's why I want to know the downstream IP address. It's very useful to me. Any diagnostic information that pound can output is extremely helpful for large commercial installations that make use of pound. Not only does it help us to diagnose ailing back end servers, but it also helps us response to customer complaints. Thank you for your understanding. -- Jake > -----Original Message----- > From: Robert Segall [mailto:[email protected]] > Sent: Wednesday, March 25, 2009 10:38 AM > To: [email protected] > Subject: Re: [Pound Mailing List] Request: add client IP to e500 error > log message > > On Fri, 2009-01-23 at 10:25 -0800, Jacob Anderson wrote: > > Hello, > > > > Can you please add the client IP to the error log when any internal > pound > > errors, e.g. e500, are generated? > > > > The current message looks something like: > > > > Jan 23 09:11:31 xxxx pound: (9d6ec003) e500 response error read from > (BE IP > > ADDR)/POST /mypath HTTP/1.1: Connection timed out (59.992 secs) > > What is your motivation for that? Knowing that an error was sent to > some > random Internet address is not very useful, and if you just test on a > local network then you already know the address. > -- > ?Robert Segall > Apsis GmbH > Postfach, Uetikon am See, CH-8707 > Tel: +41-44-920 4904 > > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
