UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Example URL:
any website serving HTTP/2 content

Steps to reproduce the problem:
1. Navigate to HTTP/2 page
2. Data is cached on disk in cache at C:\Users\{Username}\AppData\Local\Google\Chrome\User Data\Default\Cache\data_x
3. Examination of data_x file (e.g. data_2) indicates that all cached data response headers are prefixed with HTTP/1.1 despite being accessed by this protocol.

What is the expected behavior?
No, the cached response header should either not state the protocol (as per RFC 7540 (Section 8.1.2.4) which states "HTTP/2 does not define a way to carry the version or reason phrase that is included in an HTTP/1.1 status line.") or identify it correctly as HTTP/2

What went wrong?
I am assuming the lack of protocol version in the response header leads to a 'default' option where HTTP/1.1 is appended to the data_x file.

Did this work before? N/A 

Chrome version: 67.0.3396.87  Channel: n/a
OS Version: 10.0
Flash Version: 

While not impacting functionality of a user or impeding the application, it does have an impact on forensic examination of the Chrome cache as the cache is incorrectly recording the protocol version in the binary data. Thanks for looking into it.
 

Deleted: http_response_headers.PNG 852 KB

	http_response_headers.PNG 852 KB View Download

Deleted: data_2_hxd.png 612 KB

	data_2_hxd.png 612 KB View Download

Deleted: data_2 1.0 MB

data_2 1.0 MB View Download