From 5a89291321bd94c64d9b85d7e81a19ff1ec15d27 Mon Sep 17 00:00:00 2001 From: Cliff Woolley Date: Tue, 7 May 2002 22:31:38 +0000 Subject: [PATCH] Changing *any* default behavior is a bad idea without _very_ careful consideration, IMO, as it can silently break existing configs. Principle of least astonishment applies. Besides, the security argument is bubkus. Security through obscurity at best, and hardly even that. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95004 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/STATUS b/STATUS index b5f64f1508..03235b097c 100644 --- a/STATUS +++ b/STATUS @@ -1,5 +1,5 @@ APACHE 2.0 STATUS: -*-text-*- -Last modified at [$Date: 2002/05/07 19:21:49 $] +Last modified at [$Date: 2002/05/07 22:31:38 $] Release: @@ -88,7 +88,7 @@ CURRENT VOTES: to the config. Possibly go one step further and add a option to just report '2.0' instead of '2.0.x' +1: IanH, BrianP - -1: Greg + -1: Greg, Cliff I use the default response all the time to verify that a module is present and at the proper version. This information is also very handy for the module surveys, to determine what -- 2.40.0