Make use of :scheme and XForwardedProto clear and consistent in Envoy #14587
Description
It looks that :scheme pseudo-header is missing in HTTP/1.x requests, which makes it impossible to use route-based actions based on HTTP vs HTTPS scheme.
HTTP/1.1 request:
[C3][S17504616115359689975] request headers complete (end_stream=true):
':authority', 'localhost:10000'
':path', '/'
':method', 'GET'
'user-agent', 'curl/7.52.1'
'accept', '*/*'
HTTP/2 request:
[C2][S9968071387702895111] request headers complete (end_stream=true):
':method', 'GET'
':path', '/'
':scheme', 'http'
':authority', 'localhost:10000'
'user-agent', 'curl/7.52.1'
'accept', '*/*'
cc @howardjohn