Request header invalid 6415 v4 #413
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So that following headers and response still get processed Ticket: #6415
For instance, the following header may be considered as valid: Transfer-Encoding: chunked, chunked Introduces a new helper function to recognize header value tokens Ticket: #6415
|
We should run all Suricata CI with this libhtp change... |
victorjulien
approved these changes
Jan 20, 2024
|
Merged in #413, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://redmine.openinfosecfoundation.org/issues/6415
#411 with code review taken into account
and not skipping zero as we used
bstr_cmp_c_nocasenotbstr_cmp_c_nocasenorzero