Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You might take a look at your Apache2 setup's configuration file for the LogFormat directive(s) in use and then read the manual regarding the LogFormat directive itself and follow that up with reading on custom log formats. That will explain what each field is for.
Did he succeed? do you think it is a malicious or normal visit?
94.198.4.42 client source IP, this one is Russia
31/May/2012:03:55:34 +0000] - UTC timestamp
"GET" - Verb
/admin/banner_manager.php/login.php HTTP/1.1" 404 9185 " - Requested URI and they failed with a 404 - Not found.
9185 - bytes sent
"Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.16) Gecko/2009122206 Firefox/3.0.16Flock/2.5.6"- Useragent string, usually A PACK OF LIES.
I'd lockdown that "admin": URL using either .htaccess or the site's apache conf file (preferred method)
Habitual,
Nice of you to do their homework for them
A question/comment about
Quote:
I'd lockdown that "admin": URL using either .htaccess or the site's apache conf file (preferred method)
You're presuming that
Code:
/admin/
is a legitimate path on the site. If it doesn't exist, it'd be a challenge to lock it down, and unnecessary, IMO
I get hundreds, nay thousands (2838* yesterday), of attempts to GET non-existent files on my web server daily. The requests consume bandwidth (< 50 bytes each), of course, as does the return of the 404 Not Found page (~240 bytes), but they are otherwise harmless.
Yes?
Of course, if there really were a
Code:
/admin/banner_manager.php/login.php
file, then, yes, it should somehow have access restricted...but then, of course, it wouldn't be throwing a 404 error.
*1400 (so, 1/2) of those were requests for apple-touch-icon*png files, which are, I believe sent by browsers on iPhones and iPads...I've given up worrying about them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.