Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED2A2B3B9 for ; Fri, 6 Jan 2012 14:02:27 +0000 (UTC) Received: (qmail 73873 invoked by uid 500); 6 Jan 2012 14:02:24 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 73204 invoked by uid 500); 6 Jan 2012 14:02:14 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 73059 invoked by uid 99); 6 Jan 2012 14:02:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2012 14:02:11 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.163.129.117] (HELO xs.adaptr.nl) (83.163.129.117) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2012 14:02:05 +0000 Received: from [10.10.10.88] (unknown [10.10.10.88]) by xs.adaptr.nl (Postfix) with ESMTPSA id 3A28E1D8032 for ; Fri, 6 Jan 2012 15:01:43 +0100 (CET) Message-ID: <4F06FEC6.50000@adaptr.nl> Date: Fri, 06 Jan 2012 15:01:42 +0100 From: Jeroen Geilman User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111125 Thunderbird/3.1.16 ThunderBrowse/3.3.5 MIME-Version: 1.0 To: users@httpd.apache.org References: <32337932.f359VV08xi@linux-suse> <4F04A5D6.8090503@adaptr.nl> <1467052.MIT6UOcjJK@linux-suse> In-Reply-To: <1467052.MIT6UOcjJK@linux-suse> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [users@httpd] Invalid URI in request OPTIONS * HTTP/1.0 On 01/06/2012 10:23 AM, Szőts Ákos wrote: > No, I don't think so; ModSecurity just get triggered because something in > the error_log. > > "As to the OPTIONS * request failing - make sure there are no hidden > rewrite rules or other URI mangling going on." > > Thank you for the tip. Is there any (easy) way to debug which rewrite rules > were applied to a query? The server is in use, so unfortunately I cannot Enable the rewritelog and see what it says: RewriteLog /some/location RewriteLogLevel 1 If RewriteLogLevel 1 does not show you what you need to see, increase it until you do see something, but I would advise you not to run at a high loglevel for long on a production system, as it will cause a massive performance hit. > turn on/off the rules randomly. > > Ákos > > 2012. január 5. 13:49:30 dátummal Igor Cicimov ezt írta: > > [error] [client 194.38.104.110] ModSecurity: Warning. String match "Invalid > URI in request" at WEBSERVER_ERROR_LOG. ModSecurity? Protection against > using * in the URI? > > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > -- J. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org