Comment 7 for bug 839569

Note that it is impossible to determine from apache's response alone if apache is vulnerable or not. The only way to check it is to do a request with lots of overlapping ranges (like killapache does) and check if the process size increases a lot or not. On 32bit machines, the original vulnerability caused an increase by 70-90MB per process/thread. On 64bit machines, the increase was even larger.