I think only via configure server http keepalive false to protect from the attack is not enough, because the options have negative impact for openstack server performance after set the keepalive option false, so it seems is not good choice, The apache server protect from the attack is 1: too many connection reset, 2: apache access log not record all repeat log. I think apache deal with keepalive method is better.
I think only via configure server http keepalive false to protect from the attack is not enough, because the options have negative impact for openstack server performance after set the keepalive option false, so it seems is not good choice, The apache server protect from the attack is 1: too many connection reset, 2: apache access log not record all repeat log. I think apache deal with keepalive method is better.