suricata

Author	SHA1	Message	Date
Philippe Antoine	d776d72711	http: range transfering ownership of file container To make concurrency reasoning clearer	4 years ago
Philippe Antoine	3ed38d2d5d	http: avoid one lock for range append data Better structure design to ensure that one flow maximum is owning and appending into the file, adding fileOwning field. Adds also a gap field in a range buffer, so that we can feed the gap on closing, when we are protected from concurrency by a lock, (lock which got removed in the append path) Fixes memcap when encountering a duplicate while inserting in red and black tree Adds many comments	4 years ago
Victor Julien	7a797631e0	http/range: cleanup and simplification Simplify locking by using the THashData lock instead of a separate range lock. Avoid size_t in function arguments. Clean up file handling functions. Implement handling of alloc errors. Rename yaml entry to byterange Unify public api naming	4 years ago
Victor Julien	5ffc9622b3	http/range: optimize struct layout	4 years ago
Philippe Antoine	e82416a415	http/range: reassemble files from different flows with range adds a container, ie a thread safe hash table whose key is the filename keep a tree of unordered ranges, up to a memcap limit adds HTPFileOpenWithRange to handle like HTPFileOpen if there is a range : open 2 files, one for the whole reassembled, and one only for the current range	4 years ago