New issue
Advanced search Search tips

Issue 904109 link

Starred by 1 user
Status: Duplicate
Merged: issue 704146
Owner:
jarhar@chromium.org
Closed: Nov 12
Cc:
swarnasree.mukkala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Network inspector showing spdy for h2 resources from AWS CloudFront

Reported by mic...@superbiche.co, Nov 10 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce the problem:
1. Open https://www.qo.fr in Chrome
2. Open the Network tab in DevTools, reload to see the requests
3. Check the main.bundle.js request
4. Check the protocol, should be spdy
5. Do the same in Firefox Developer Edition, see a h2 resource for the same file

What is the expected behavior?
Network inspector should properly show the resource as h2 (it does for the page resource - html is on EC2 - which is showed as h2)

What went wrong?
The network inspector shows http/2 resources from CloudFront as using spdy protocol instead of h2. 
It properly shows HTML coming from EC2 instance as h2. 
In other browsers (Firefoxdev) resources coming either from CloudFront or EC2 are properly shown as using h2 protocol

Did this work before? N/A 

Chrome version: 70.0.3538.77  Channel: n/a
OS Version: OS X 10.14.1
Flash Version:
chrome-network.png
622 KB View Download
chrome-network-details.png
601 KB View Download
firefoxdev-network.png
401 KB View Download
firefoxdev-network-details.png
463 KB View Download

Comment 2 by phanindra.mandapaka@chromium.org, Nov 10

Labels: Needs-Triage-M70

Comment 3 by swarnasree.mukkala@chromium.org, Nov 12

Cc: swarnasree.mukkala@chromium.org
Labels: Triaged-ET Target-72 M-72 FoundIn-71 FoundIn-70 FoundIn-72 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version #70.0.3538.77 and latest chrome #72.0.3608.0 using Windows 10, Mac 10.14 and Ubuntu 17.10 by following steps as per comment#0.

This behaviour is seen from old M-60(#60.0.3112.0) builds. This is a non-regression issue, hence marking it as untriage and requesting someone from dev team to look into the issue.
Thanks.!

Comment 4 by lushnikov@google.com, Nov 12

Owner: jarhar@chromium.org

Comment 5 by jarhar@chromium.org, Nov 12

Mergedinto: 704146
Status: Duplicate (was: Untriaged)
I already fixed this issue with this change: https://chromium-review.googlesource.com/c/chromium/src/+/1268959
I verified that https://www.qo.fr doesn't show any "spdy" requests in my development build, 72.0.3609.0, as well as Canary on Mac 10.14, 72.0.3608.0.
According to omaha proxy, my fix first landed in 71.0.3574.0, which explains why the bug is still showing in release 70.
swarnasree.mukkala@ are you sure you were able to reproduce on 72.0.3608.0?

Comment 6 by swarnasree.mukkala@chromium.org, Nov 13 

In reply to comment#5.

@jarhar: When triaged by following the steps as per issue id:704146(Comment#11). Able to reproduce the issue on reported chrome version #70.0.3538.77 and able to verify fix on chrome version #72.0.3608.0 using Windows 10, Ubuntu 17.10 and Mac 10.13.6. 
Attached screenshots for reference.
Thanks.!
904109(M72).png
383 KB View Download
904109_M70.png
710 KB View Download

Comment 7 by mic...@superbiche.co, Nov 13 

I confirm that 72.0.3608.4 Canary shows proper H2 requests. Thanks Chromium team!
►

Sign in to add a comment