You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is based on the comment #960 (review) : if tfw_http_resp_process() falls to bad_msg label, then the error/attack treatment is delegated to tfw_http_srv_error_resp_and_log(). If error responses are configured (reply parameter is true), them everything is fine. However, if we just block the response (reply is false), then current request and responses are just dropped and we continue to process next client requests. This way we break request-response sequence which we must not do.
If we block a response (as well as request), then we have to terminate client connection in respect to pipelined requests.
The text was updated successfully, but these errors were encountered:
The issue is based on the comment #960 (review) : if
tfw_http_resp_process()
falls tobad_msg
label, then the error/attack treatment is delegated totfw_http_srv_error_resp_and_log()
. If error responses are configured (reply
parameter is true), them everything is fine. However, if we just block the response (reply
is false), then current request and responses are just dropped and we continue to process next client requests. This way we break request-response sequence which we must not do.If we block a response (as well as request), then we have to terminate client connection in respect to pipelined requests.
The text was updated successfully, but these errors were encountered: