Need some help please

[James46]

My log file is getting really big with a lot of these.
- - [24/Apr/2004:06:47:15 -0400] "GET / HTTP/1.1" 200 8192
- - [24/Apr/2004:06:43:52 -0400] "GET / HTTP/1.1" 200 13071
These two is the most that's being put in the log file and I have no ideal what it is thats being taken. Is what's in the / / a folder?, and I don't know what the 1.1 means. can some one explain this please.

[JohnKelly]

"/" means the default document for a domain (generally index.html or index.htm). So you would likely see that every time someone visits www.yourdomain.com

HTTP 1.1 is the protocol used for browsers, this is also normal.

[James46]

Thank you JohnKelly
So the 13078 past the 200 is the index html, your right, I look at the index and it's that size. What I don't under stand is how come there is nothing else in the log file past that first index html file. What I meen is if I load up the website from another computer and I then look at the access log file, the first line is the "GET / HTTP/1.1" 200 13071 and also 28 other lines in the access log file as well.
Does this meen that the other people are not letting the hole website load up and just leveing before the rest of the webpage loads up. I think if that's true then these people are on dialup with lest than 56k modems. I've had people here that is on dialup and useing a 56k moden and they say that it don't take the webpage that long to loadup.

[Powdork]

Is it possible you have some js that loads with the page and viewers without js enabled are viewing it?

[nalin]

Likely the other 28 lines are graphics - your log trails are likely robots though its hard to tell without knowing the log format.

If there is a useragent associated with other log entries then these are most likely spiders (probably of a malicious type as they seem not to have fetched and therefore are disreguarding robots.txt).

If you are not logging useragent then this could be text based browsing (such as lynx) or users who have configured their browser not to display images, or wget, or a million other things - your best bet would be using a more robust log format (replace your CustomLog with "CustomLog logs/access_log combined").