Jeff Trawick wrote:
On 3/16/07, Karl Chen [EMAIL PROTECTED] wrote:
On 2007-03-05 13:24 PST, Joe Orton writes:
Joe On Mon, Mar 05, 2007 at 09:33:56PM +0100, Ruediger Pluem wrote:
On 03/03/2007 05:47 AM, Karl Chen wrote: present. Also
other issues like noise in the log file.
On 2007-03-05 13:24 PST, Joe Orton writes:
Joe On Mon, Mar 05, 2007 at 09:33:56PM +0100, Ruediger Pluem wrote:
On 03/03/2007 05:47 AM, Karl Chen wrote: present. Also
other issues like noise in the log file. I've also seen
people complaining that GET / might incur the cost of
On 3/16/07, Karl Chen [EMAIL PROTECTED] wrote:
On 2007-03-05 13:24 PST, Joe Orton writes:
Joe On Mon, Mar 05, 2007 at 09:33:56PM +0100, Ruediger Pluem wrote:
On 03/03/2007 05:47 AM, Karl Chen wrote: present. Also
other issues like noise in the log file. I've also seen
On 2007-03-17 11:19 PDT, William A Jr Rowe writes:
William Karl - you can pretty easily toggle requests with
William mod_log_custom and either mod_setenvif or mod_rewrite
William to not appear in the log, I'll leave that as an
William exercise to the reader (or efficient google
Hi, I just spent 1-2 hours tracking down what turned out to be
internal dummy connection. In my log files I get a ton of:
::1 - - [02/Mar/2007:19:31:22 -0800] GET / 400 705 - -
For others, at least the log line would say Apache/... (internal
dummy connection), for easy Googling; for me,
Karl Chen wrote:
Would it be possible to connect to a non-SSL port, if possible, so
at least the string internal dummy connection shows up?
Even better would be to not show that string at all. When I
connect to httpd and close the connection without sending
anything,
Not sending
On 03/03/2007 05:47 AM, Karl Chen wrote:
present. Also other issues like noise in the log file. I've also
seen people complaining that GET / might incur the cost of
dynamic content generation for /.
Hm. Just thinking loud. Can we avoid this if we replace GET / with OPTIONS /?
Would it
Ruediger Pluem wrote:
On 03/03/2007 05:47 AM, Karl Chen wrote:
present. Also other issues like noise in the log file. I've also
seen people complaining that GET / might incur the cost of
dynamic content generation for /.
Hm. Just thinking loud. Can we avoid this if we replace GET /
William A. Rowe, Jr. wrote:
Ruediger Pluem wrote:
On 03/03/2007 05:47 AM, Karl Chen wrote:
present. Also other issues like noise in the log file. I've also
seen people complaining that GET / might incur the cost of
dynamic content generation for /.
Hm. Just thinking loud. Can we avoid
On Mon, Mar 05, 2007 at 09:33:56PM +0100, Ruediger Pluem wrote:
On 03/03/2007 05:47 AM, Karl Chen wrote:
present. Also other issues like noise in the log file. I've also
seen people complaining that GET / might incur the cost of
dynamic content generation for /.
Hm. Just thinking loud.
10 matches
Mail list logo