libhtp
libhtp copied to clipboard
OISF
LibHTP is a security-aware parser for the HTTP protocol and the related bits and pieces.
See #362 for previous version. ### Changes since last version * Test the data in each callback call separately. ### Testing/QA I ran `make check` to make sure existing tests...
We found a bug where the response body data callback is getting called repeatedly with the same (ever growing) data. Internally, I think this occurs when `RES_LINE` state treats incoming...
decompression: use less function pointers as it is always the same function anyways Replaces #357 with keeping the exported struct fields even if we no longer use them Replaces #359...
This adds support for Bearer type authorization header. Incorporated suggestions by @catenacyber at https://github.com/OISF/libhtp/pull/325#pullrequestreview-620194346: - defined `HTP_AUTH_BEARER` constant, - added test file and `TEST_F(ConnectionParsing, AuthBearer)` using example from RFC6750. Fixes...
See: http://tools.ietf.org/html/rfc2616#section-3.6.1 i.e.: part of my code in python, where I construct special crafted query. ``` query = '\r\n'.join([ b'POST /qwe.asd HTTP/1.1', b'Host: ' + TEST_HOST, b'Transfer-Encoding: chunked', b'Content-Encoding: gzip',...
Multipart/form-data messages have field name listed in Content-Disposition header field. It's something like `name="field1"`. Libhtp parses such messages just fine. However, at least some platforms also accept `name=field1`, without double...
hello，I think that Transfer-Coding and Content-Encoding should be only supported by the response direction.
Related to #13 which was closed for no apparent reason. As soon as server replies with 101 Switching Protocols, anything after HTTP headers is no longer HTTP protocol. > The...
