f2b02cfd94
The error handling in the HTTP payload forwarding is far to be ideal because both sides (request and response) are tested each time. It is espcially ugly on the request side. To report a server error instead of a client error, there are some workarounds to delay the error handling. The reason is that the request analyzer is evaluated before the response one. In addition, errors are tested before the data analysis. It means it is possible to truncate data because errors may be handled to early. So the error handling at this stages was totally reviewed. Aborts are now handled after the data analysis. We also stop to finish the response on request error or the opposite. As a side effect, the HTTP_MSG_ERROR state is now useless. As another side effect, the termination flags are now set by the HTTP analysers and not process_stream(). |
||
|---|---|---|
| .. | ||
| common.pem | ||
| h1_host_normalization.vtc | ||
| h1_to_h1.vtc | ||
| h2_desync_attacks.vtc | ||
| h2_to_h1.vtc | ||
| http_abortonclose.vtc | ||
| http_bodyless_response.vtc | ||
| http_msg_full_on_eom.vtc | ||
| http_request_buffer.vtc | ||
| http_splicing.vtc | ||
| http_transfer_encoding.vtc | ||
| http_wait_for_body.vtc | ||
| protocol_upgrade.vtc | ||
| scheme_based_normalize.vtc | ||
| srv_ws.vtc | ||
| websocket.vtc | ||