Feature #1576
http: byte-range support
Effort:
Difficulty:
Label:
Description
Not currently supported by libhtp: https://github.com/OISF/libhtp/issues/58
Some discussion: https://lists.openinfosecfoundation.org/pipermail/oisf-devel/2015-October/003492.html
Related issues
History
Updated by Victor Julien over 1 year ago
- Related to Feature #2485: http: log byte range with file extraction added
Updated by Raymond Hansen 9 months ago
First step would be to document the chunks of file(s) as identified per sensor, if multiple sensors are in use.
Updated by Victor Julien 6 months ago
- Has duplicate Bug #2326: File extraction not properly handling http range requests added
Updated by Victor Julien 5 months ago
- Related to Feature #1017: Add support for content-range added
Updated by Philippe Antoine 3 months ago
My understanding is the following :
We now log the byte-range but we would like suricata to handle the complete file reassembly (in case there is any).
Is that correct ?
Is there already an example of suricata of reassembly over TCP ? And in this case over different flows ?