t;-"
time span - 2 hrs
count - 186157
84.19.174.28 - - [01/May/2015:22:12:49 +] "POST /wp-login.php HTTP/1.0"
200 10995 "-" "-"
time span - 8 hrs
count - 107285
-Original Message-
From: Eric Covener [mailto:cove...@gmail.com]
Sent: Tuesday,
On Mon, May 4, 2015 at 7:33 PM, Joshua Smith wrote:
> In both cases, when i monitored my site with the 'server-status' module, the
> ip address was still there, with sometimes more than 30 requests, and all
> for the same page, which was /login.php. And it continued to be there
> for the next
atements are just ignored unless they come after rewriteengine on ?
Thanks,
Josh
-Original Message-
From: Richard [mailto:lists-apa...@listmail.innovate.net]
Sent: Monday, May 04, 2015 20:27
To: users@httpd.apache.org
Subject: Re: [users@httpd] Deny didn't work
Also "allow/
Also "allow/deny" (or the 2.4 equiv) directives only control whether
the server delivers the content, not whether the client can request
an item from the server. I.e., the indication of successful blocking
will be the response code changing from 200 to 403, but you'll still
likely see hits. If you
What version of Apache are you using?
Apache 2.4 changed the access control directives unless you specifically
enable the old style: http://httpd.apache.org/docs/2.4/upgrading.html#access
Also, make sure you have the correct AllowOverride statements.
- Y
On Mon, May 4, 2015 at 7:33 PM, Joshua Sm
Hi,
I tried both of the following methods to block an ip address, but neither
worked. In .htaccess, I put:
Order Deny,Allow
Deny from 123.123.123.123
and
RewriteCond %{REMOTE_ADDR} ^123.123.123.123
RewriteRule .* /maintenance.html [R=503,L]
(I do have the mod_rewrite module instal
