WAF causes a timeout when a request has Transfer-Encoding: chunked in the headers

Question

As it says in the title, WAF is causing a timeout for a connection that has Transfer-Encoding: chunked in the headers of the request. It appears to happen when it is a GET request with nothing in the body.
It is never hitting any of the rules. 
This feels like a bug to me, since there is no way to control this with any of the Rules if it isn't getting that far.

How can I report this bug, or get a solution? As it is, we will have to stop using a WAF in front of our load balancers if there are random invisible timeouts caused like this.

And yes, we know that that header is meaningless when the body is empty. Just concerned about the invisible failure.

Answer

Hi,

Thank you for contacting AWS Re:post .

I understand you have some clarifications regarding WAF causing timeouts for a connection that has Transfer-Encoding: chunked in the headers of the request.

Looking at the issue, This would require further analysis and troubleshooting. 
 I would suggest you to open a case with the WAF premium support team and provide details such as:

--> Network Architecture
--> Network Traffic Flow 
--> Any supported Logs (Access logs)
--> Error output

Thanks and have a nice day!

Answer

I'm running into the same issue. Has this been answered?

Thank you

WAF causes a timeout when a request has Transfer-Encoding: chunked in the headers

Relevant content