Is there any ticket for this bug, or is it fixed internally?
I just want to check whether it's really a bug, before I start to debug for
some hours.
If it's convenient for you, I can also check the source RPM (just tell me
what should I search).
Ákos
2012. január 6. 09:34:22 dátummal Eric Cov
Looks like a recent bug backported into your 2.2.21
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@
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 t
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
[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?
On Thu, Jan 5, 2012 at 6:17 AM, Jeroen Geilman wrote:
> On 01/04/2012 12:36 PM, Szőts Ákos wrote:
>
>> Hi All,
>>
>> There's a
On 01/04/2012 12:36 PM, Szőts Ákos wrote:
Hi All,
There's a frequent error message in my Apache error_log (v2.2.21 under
openSUSE 12.1):
"Invalid URI in request OPTIONS * HTTP/1.0"
I know this is an internal dummy connection to test if the server is alive
or not. But every time, Apache tries to
Hi All,
There's a frequent error message in my Apache error_log (v2.2.21 under
openSUSE 12.1):
"Invalid URI in request OPTIONS * HTTP/1.0"
I know this is an internal dummy connection to test if the server is alive
or not. But every time, Apache tries to connect to itself, it writes
instead of
