> CustomLog logs/range.log "%r %{Range}i" env=bad-range
>
Actually I was only using that to show/debug the result of the
directives, did not occur that folks would also want to log these!
Of course that makes sense though.
Unfortunately we lose the range header in the log when we zap it, so
logging it is not really so useful in concert with the conditional.
so probably just wise to collect them under common logformat:
SetEnvIf Range (,[^,]*){5,} bad-range=1
RequestHeader unset Range env=bad-range
CustomLog logs/range.log common env=bad-range
--
Eric Covener
cove...@gmail.com
