1325925 - First request of HTTP/2 via HTTP proxy will record as HTTP/1.1

Status: NEW

(DevTools :: Netmonitor, defect, P3)

Description

[chhsiao90]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36

Steps to reproduce:

1. Preferences -> Advanced -> Network -> Settings
2. Select Manual proxy configuration and set SSL Proxy to my own http proxy
3. Open Developer Tool and select to Network tab
3. Open https://www.google.com


Actual results:

Find that the first record's protocol is HTTP/1.1
Other records' protocol are HTTP/2


Expected results:

The first record's protocol should be HTTP/2

Comment 1

[Locke Chen]

Hi Honza
I'd like work on this. Could you please assign to me? :)
Thank you!

Comment 2

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Done!

Honza

Comment 3

[Locke Chen]

Hi Honsa
Looks like this is not an issue.
I think the first HTTP/1.1 message is from proxy server.
You also can try to get free SSL proxy to test it. 
link: https://www.sslproxies.org/

I have see HTTP/1.1, but just happen on first time connection.

Comment 4

[Locke Chen]

steps:
setting ssl proxy first then open https://www.google.com.
You can see first requst is 'HTTP/1.1' at this time.
now reload this page, this request was no longer exist.(I mean the HTTP/1.1 request.)

Comment 5

[Jan Honza Odvarko [:Honza] (always need-info? me)]

@chhsiao90: are you still experiencing the problem?

Honza

Comment 6

[chhsiao90]

Yes, I will expect the first request via proxy connect to a HTTP/2 service should display HTTP/2 as the protocol.

Here is the reason why I think it should be HTTP/2, not HTTP/1.1.
When firefox first connect to https://www.google.com via proxy, it actually send two requests.
One is a CONNECT request to the proxy with protocol HTTP/1.1, and the other is the GET request to www.google.com via proxy with protocol HTTP/2.
I expected the netmonitor will record the second request, but it actually record the second request's content with first request protocol.

The HTTP/1.1 will mislead the developer that using the tool for debug, think that the request/response is on the protocol HTTP/1.1, but it actually on HTTP/2.