Project

General

Profile

Actions
Copy link

Optimization #4555

closed

HTTP2: what to do when HTTP upgrade is requested and HTTP2 is disabled ?

Added by Philippe Antoine over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Philippe Antoine
Target version:
7.0.0-beta1
Effort:
Difficulty:
Label:
Needs backport to 6.0

Description

Currently, Suricata expects a protocol change, but fails to recognize HTTP2 when it is disabled, leading to APPLAYER_UNEXPECTED_PROTOCOL

Related issues 1 (0 open — 1 closed)

Copied to Suricata - Optimization #4642: HTTP2: what to do when HTTP upgrade is requested and HTTP2 is disabled ?ClosedShivani BhardwajActions
Actions
Copy link
 #1

Updated by Jeff Lucovsky over 3 years ago

  • Copied to Optimization #4642: HTTP2: what to do when HTTP upgrade is requested and HTTP2 is disabled ? added
Actions
Copy link
 #2

Updated by Victor Julien over 3 years ago

  • Assignee set to Philippe Antoine
Actions
Copy link
 #3

Updated by Victor Julien over 3 years ago

This probably needs some special case handling, but I'd say we disable app-layer but keep raw reassembly going. So rules inspecting stream content would still work.

Actions
Copy link
 #4

Updated by Philippe Antoine over 3 years ago

  • Status changed from New to In Review
Actions
Copy link
 #5

Updated by Philippe Antoine about 3 years ago

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: Atom PDF