once I experienced similar problem with spammer looking for
vulnerabilities
in my feedback form scripts. Of course he used proxies, so denying by IP
would have no sense.
So I hide the script behind a single shtml page, so that no one could ever
know what the real name of any script is. All cgi r
On Fri, June 23, 2006 2:09 pm, Mike Jackson wrote:
The obvious: Age restrictions on pr0n.
Well duh.. I'd think anyone on an APACHE list would know that. :-D
But of course, though mine is IP and user/pass protected. Ahem.
How Apache would tell the user's age
is anyone's
So of course, seeing a bunch of messages with that subject, I was somewhat
curious why someone would want to deny access based on AGE... Ohh. Never
mind. Maybe I don't want to know.
The obvious: Age restrictions on pr0n. How Apache would tell the user's age
is anyone's guess, but that would be
RewriteCond %{HTTP_USER_AGENT} '^Mozilla'
RewriteRule ^/(.*) http://www.blah.com/ [L,R]
That would also block most legitimate traffic as well - most browsers report
that they're a variant of Mozilla. Better to match on something more unique
to that user agent, like
RewriteCond %{HTTP_USER_A
I found an entry in access log that seems strange to me:
192.168.2.101 - - [22/Jun/2006:15:31:27 +0200] "POST /standard.php
HTTP/1.1" 200 16639 "https://192.168.2.4/standard.php,
https://192.168.2.4/standard.php, https://192.168.2.4/standard.php";
"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0
I am using a simple system call:
system("notepad.exe");
I hate to suggest a simple solution, but have you tried specifying the full
path to the executable? I've never used a WAMP setup (other than installing
XAMPP, saying "oh, cool," then forgetting all about it until now), but that
looks lik
I'm running FC4. When my php script hits mysql_connect() it dies. I
checked error_log and found
PHP Fatal error: Call to undefined function mysql_connect()
What am I missing in my httpd.conf file?
That sounds like a question for a PHP mailing list ;)
But, it also sounds like PHP doesn't h
Hello to all,
Is there a way though httpd proxy to "show" the arguments sent with a
POST method? I have been trying to find a way to reveal arguments from
our java application that are POST method to the server... for example
http://someserver/TspLogin.do;jsessionid=HDFDFDDFDFD?Username=tes
I noticed something odd in my logs this morning. Someone tried sending this
request to one of my servers:
CONNECT xx.xx.xx.xx:25 HTTP/1.0
The server returned a 302, with a Location: of http://127.0.0.1, which I
verified by telnetting to port 80 and trying it myself. This particular
server is
Apart from certain usage - like MP3 or video streaming on a 100 or
1000Mbps line -, the bottleneck is not the disk subsystem, but the CPU is,
the average load of 2 also shows this. Using a RAID1 array also decreases
stress on the disks, the 4.5% iowait avg is not an issue - and logging
into differ
I'm running a couple Redhat servers with Apache 1.3.36 (which my company is
sticking with for legacy reasons; I'm sure we'll move to 2.0 or 2.2
eventually, but everyone here other than me has only used 1.3). It's a
typical LAMP setup. There's about 250 virtual hosts on a handful of IPs on
the s
All the configs are shared across NFS. So config files are the same on
both OH1 and OH2...
the applications connect to mysql via php connect strings, and as tcpdump
reveals are doing the proper things
You might try using strace on an Apache process on OH2 and see if you can
spot anything am
12 matches
Mail list logo
