Do PAN firewalls support inspection of HTTP2 traffic in the same way as they do HTTP1.x? I am curious because HTTP2 has three main improvements in this version, and I could see these the following two features potentially causing issues for HTTP1.x decoders: A new HTTP method, PUSH. "Server Push allows the server to “bundle” assets that the client didn’t ask for" (Cloudflare) which "can be useful when the server knows the client will need to have those responses available in order to fully process the response to the original request." (httpwg.org) HTTP Header Compression. "HTTP header fields used in a connection can contain large amounts of redundant data, frames that contain them are compressed" (httpwg.org) I am curious about PAN support for HTTP2 becuase: For Number 1: Would any App or Threat signature that uses the HTTP "GET" method as a qualifier will not fire when data is PUSHed to a client? For Number 2: Does the PAN have the right decoders and routines (eg, know to decompress the header) to handle compressed headers? I assume a lot of app-IDs, especially for SSL encrypted flows, look at things in the HTTP header to determine the App in use.
... View more
