Since we upgraded our BIG-IP F5 from 126.96.36.199 to 188.8.131.52, we encountered a loss of POST requests between virtualserver and our backend. This is always the same request which is blocked.
Firstly, we were thinking that the problem was on the backend side because we were able to log HTTP_REQUEST_RELEASE event everytime. But we decide recently to roolback and the problem disappears.
In order to troubleshoot, we have mounted a temporary virtual server on which we redirect only the specific request.
And then, we were able able to observe that the HTTP_REQUEST_RELEASE occurs every time on the first virtualserver but on the temporary one, we only see CLIENT_ACCEPTED and CLIENTSSL_HELLO. Sometimes the request works and we can see HTTP events on this one.
Any help is appreciated !
Packet capture can help you troubleshoot the issue.
Starting from v16.1.0, a new feature available in the HTTP profile. Allow space title name feature, which is disabled by default, may be triggering this issue.
Allow Space Header Name: Specifies whether to allow white space in an HTTP header between the header name and the separator colon in an HTTP request or response. When Enabled, the BIG-IP system ignores white space between the header name and the colon. This feature is disabled by default.
Thanks a lot for your answer.
I've tried to pass the value of tmm.http.rfc.allowwsheadername to disable in v184.108.40.206 and I didn't manage to reproduce the issue.
To be sure, I'll enable the setting concerned in v17 and see if the problem disappears.
We can confirm that the bug was introduced in v16, we upgraded to v15 and the bug disappeared. We looked for similar issues that appeared in v16 but didn't find anything conclusive. any help would be most welcome.