Skip to content

Conversation

catenacyber
Copy link
Contributor

@catenacyber catenacyber commented Mar 19, 2025

As it can happen in midstream case or gap
And the response may be handled as HTTP/0.9

Edit :
QA has same errors as OISF/suricata#12828 and next versions

As it can happen in midstream case or gap
And the response may be handled as HTTP/0.9
@suricata-qa
Copy link

WARNING:

field baseline test %
SURI_TLPR1_stats_chk
.app_layer.error.http.parser 536 485 90.49%

Pipeline 25257

@catenacyber
Copy link
Contributor Author

So, I think this is good and will require a QA rebaseline

@victorjulien
Copy link
Member

Can you create SV tests for these cases?

@catenacyber
Copy link
Contributor Author

Can you create SV tests for these cases?

Which cases ? The remaining errors ? (not direct as it comes from TLPR)

@victorjulien
Copy link
Member

"As it can happen in midstream case or gap
And the response may be handled as HTTP/0.9"
This case ^

@catenacyber
Copy link
Contributor Author

"As it can happen in midstream case or gap And the response may be handled as HTTP/0.9" This case ^

Spent too much time building OISF/suricata-verify#2372
Not sure I found the original case that led to this commit message...

@catenacyber
Copy link
Contributor Author

New commit message in #450

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants