Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

http2: remove http2.header keyword #8615

Closed
wants to merge 1 commit into from

Conversation

catenacyber
Copy link
Contributor

Link to redmine ticket:
https://redmine.openinfosecfoundation.org/issues/5780

Describe changes:

  • http2: remove http2.header as it is confusing with http.header
  • Keep the functionality with keywords http2.request_header and http2.response_header which match an individual header

@victorjulien do you also want to add the individual header matching on HTTP1 ? and have the keyword be http.request_header

As it had a different behavior than http.header and this was
confusing.

The behavior of matching on only one header at a time
is now available through the http.request_header and
http.response_header keywords.

Ticket: OISF#5780
@catenacyber
Copy link
Contributor Author

Previous PR was #8371

@catenacyber
Copy link
Contributor Author

Looks like I need to modify S-V tests...

@suricata-qa
Copy link

WARNING:

field baseline test %
SURI_TLPW1_stats_chk
.flow.end.tcp_state.last_ack 1004 257 25.6%
.tcp.rst 145769 113397 77.79%
SURI_TLPR1_stats_chk
.flow.end.tcp_state.fin_wait2 156072 127814 81.89%

Pipeline 12794

@victorjulien
Copy link
Member

The ticket suggests doing just http.request_header/http.request_headers, not specific http1 and http2 variants.

@catenacyber
Copy link
Contributor Author

Going on in #8621

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