in reply to Re^15: Question about the most efficient way to read Apache log files without All-In-One Modules from CPAN (personal learning exercise)
in thread Question about the most efficient way to read Apache log files without All-In-One Modules from CPAN (personal learning exercise)
3. So, I reminded you: "He did ask for a learning exercise; not a pre-solved solution.".
At no point did I provide a pre-solved solution, I simply indicated directions to pursue, just like you did. Except I provided 2 different ones that were more likely to be useful. Sorry about that; I'll try to do worse next time.
4. So you come back with this guess: "(or if Apache really does go to some pains to make sure spaces never show up in the various log fields -- say by always representing them as + or %20 -- then yay, but I'm not sure this is actually true.)".
Which is demonstrably wrong!
Which inexplicably links to the HTTP/URI specs, which as I have repeatedly pointed out has nothing to do with this. (I'm beginning to wonder if I know more about the innards of Apache than you do)
5. You retort with: "which says nothing about logname and user,".Right. The regexp which doesn't always get used (which you'd know if you'd bothered to read the code at least as carefully as I did, which I'll admit wasn't all that carefully, but sufficed...).
Look at the regex above! Wrong again.
6. And "nor does it guarantee that the HTTP command field always consists of exactly 3 space-separated components ".Oh look, another link to the HTTP spec. Meanwhile, I provide not one but TWO sources of counterexamples (script kiddies, and 408 lines, neither of which are particularly rare) that could lead to the HTTP command in the log file not consisting of 3 space-separated components -- the sorts of things that would screw up a split solution ... that the OP would most likely want to know about (and are hence worth mentioning)
Also wrong!
7. So then you throw "10.54.33.35 - - 18/Jun/2015:09:05:55 -0700 "-" 408 0" into the mix.Yet another statement pulled out of your ass that turns out not to be true which then has to be corrected (again Apache::Log::Parser works just fine, thank you very much)
And, as I've shown above, that would (without special handling) break most pre-solved solutions;
which I'll remind you: the OP explicitly didn't want.Never mind that you are the only one in this thread who's been bringing up pre-solved solutions.
So who exactly is wasting everybody's time again?
This is exactly the sort of behavior that you decry in others. Heaven forbid anybody should call you out on your own bullshit.