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
{{ message }}
This repository has been archived by the owner on Jun 30, 2021. It is now read-only.
evhtp_hook_on_conn_error is never used. A quick search of the repo only shows this hook being set here evhtp.c:4325 evhtp_hook_on_error isn't used if only set in struct evhtp_connection_s. It must be explicitly set on every request struct. evhtp.c:758
Partial Workaround
Use evhtp_hook_on_path to set it on the evhtp_request_t with evhtp_request_set_hook(). However on_error will only be called if the connection get's to this callback. For Example
The functions htp_hook_error_() is only called for request-ish errors
while htp_hook_connection_error_() is only called for connection-ish
errors.
This mainly applies to the following functions:
`htp__connection_readcb_` :
if `EVHTP_RES_DATA_TOO_LONG` is the connection request return value,
both `hook_error_()` and `hook_connection_error()` are called.
if there is a parser error, `hook_connection_error_()` is called
with the error type of `EVHTP_RES_PARSER_ERROR`
`evbuffer_drain` is now called before the connection request status
switch/case statement, and `EVHTP_RES_PAUSE` is now a case (moved)
`htp__connection_eventcb_`
!!!!! PLEASE MAKE NOTE OF THIS CHANGE !!!!!
this function now calls `htp__hook_connection_error_()` but no
longer calls `htp__hook_request_error_()` to match the naming
scheme.
prior to this, both request_error and connection_error was called
within this function.
Details
evhtp_hook_on_conn_error
is never used. A quick search of the repo only shows this hook being set here evhtp.c:4325evhtp_hook_on_error
isn't used if only set instruct evhtp_connection_s
. It must be explicitly set on every request struct. evhtp.c:758Partial Workaround
Use
evhtp_hook_on_path
to set it on theevhtp_request_t
withevhtp_request_set_hook()
. However on_error will only be called if the connection get's to this callback. For ExampleSteps or code to reproduce the problem.
on_conn_error
andon_error
nc localhost 8080
Example code (if applicable)
Version
1.2.16
The text was updated successfully, but these errors were encountered: