---
title: "Comment by Peter Potrowl on \"Exploiting HTTP Parsers Inconsistencies\" | Hashnode"
description: "Hi! Awesome! Unfortunately, you don&#39;t mention Apache... Does it have the same kind of behavior? Thanks!"
url: "https://hashnode.com/posts/exploiting-http-parsers-inconsistencies/648dec85578b47894c6af863/comment/6523fe582e0ccdd34cf47e75"
---

[Discussion](https://hashnode.com/posts/exploiting-http-parsers-inconsistencies/648dec85578b47894c6af863)

Comment [Exploiting HTTP Parsers Inconsistencies](https://hashnode.com/posts/exploiting-http-parsers-inconsistencies/648dec85578b47894c6af863)

[Peter Potrowl](https://hashnode.com/@Peter17)

[Oct 9, 2023](https://hashnode.com/posts/exploiting-http-parsers-inconsistencies/648dec85578b47894c6af863/comment/6523fe582e0ccdd34cf47e75)

Hi! Awesome! Unfortunately, you don't mention Apache... Does it have the same kind of behavior? Thanks!

[Rafael da Costa Santos](https://hashnode.com/@rafax00)

[Oct 9, 2023](https://hashnode.com/posts/exploiting-http-parsers-inconsistencies/648dec85578b47894c6af863/comment/6523fe582e0ccdd34cf47e75#reply-652401602e0ccdd34cf47f15)

Hi, thanks!

I didn't mention Apache because I wanted to focus on findings that have a security impact, and it's not prone to any related behavior.

Regarding parsing the HTTP protocol, my tests showed that Apache is the secured solution.
