Implement content inspection that does not require buffering #170
Labels
2.x
Related to ModSecurity version 2.x
3.x
Related to ModSecurity version 3.x
enhancement
RIP - Type - Feature
MODSEC-17: In order to block 100% reliably we need to buffer; there's no question about that. However, buffering is not always the best, or even desired, approach. Some mechanisms (such as file upload progress bars) rely on having a free flow of data, and there also may be latency issues with very large request and response sizes. Furthermore, turning buffering off when in DetectionOnly mode will make ModSecurity more transparent and reduce memory consumption. This ticket outlines a proposal how to improve on our current handling on content inspection in this respect:
The text was updated successfully, but these errors were encountered: