Annoying crx calls with Chrome

Support
1

Hello,

When testing with Chrome, I found annoying *.crx calls in waterfalls.
I’ve tried to block them but without success.

It seems to be chrome extension updates.

Is there a way to eliminate them ?

Thx

call #1

URL: http://redirector.gvt1.com/crx/blobs/QgAAAC6zw0qH2DJtnXe8Z7rUJP3JhGfde_qB0i4AGFheiw2tTb3K6LcQf20IP74eoXNHAIX8nIOYdFWOToDjV8cZQ94IPWaaT-I78bm_QX7OYnNlAMZSmuW4A7eviT39bqZoLgRHXkZ6Ztnrrw/extension_0_1_2_0.crx
Host: redirector.gvt1.com
IP: 216.58.208.238
Error/Status Code: 302
Client Port: 1708
Start Offset: 0.732 s
Time to First Byte: 79 ms
Content Download: ms
Bytes In (downloaded): 1.5 KB
Bytes Out (uploaded): 0.5 KB

Call #2

URL: http://r20---sn-25g7sm76.gvt1.com/crx/blobs/QgAAAC6zw0qH2DJtnXe8Z7rUJP3JhGfde_qB0i4AGFheiw2tTb3K6LcQf20IP74eoXNHAIX8nIOYdFWOToDjV8cZQ94IPWaaT-I78bm_QX7OYnNlAMZSmuW4A7eviT39bqZoLgRHXkZ6Ztnrrw/extension_0_1_2_0.crx?cms_redirect=yes&expire=1438940610&ip=193.252.243.91&ipbits=0&mm=31&mn=sn-25g7sm76&ms=au&mt=1438926087&mv=m&nh=EAI&pl=24&sparams=expire,ip,ipbits,mm,mn,ms,mv,nh,pl&signature=150F084BD80407164090F7526BAB65542FD260C5.34234047E71E86F8CF7F8E687BB28522FCDC8620&key=cms1
Host: r20---sn-25g7sm76.gvt1.com
IP: 208.117.236.153
Error/Status Code: 200
Client Port: 1733
Start Offset: 0.931 s
DNS Lookup: 59 ms
Initial Connection: 59 ms
Time to First Byte: 115 ms
Content Download: 3371 ms
Bytes In (downloaded): 179.0 KB
Bytes Out (uploaded): 0.7 KB

2

Private instance or here on the public instance? I’ve been playing whack-a-mole with the extension updates and recent agent updates should have them blocked but if not it would help to see a failure so I can add more blocking to the agents.

3

I’m seeing this issue with Chrome from the Manchester instance at the moment. It’s skewing a lot of stats.

4

ok, I just pushed an update that expanded the blocking and that appears to have fixed it. Let me know if you see any more crx downloads sneak in.

5

Hey Patrick it seems like it came back. Happening on different sites I am testing, but here is a good example: WebPageTest Test - WebPageTest Details

Any solution planned?

Thanks,

John

6

Sorry, there was a change made over the weekend to show requests where the connection failed (for SPOF, etc). It looks like that also accidentally picked up showing the blocked Chrome requests.

I just made a change to filter those out of the reporting. It’ll take about an hour for it to roll out but they should be gone after that.

7

Actually, that’s just the clienst1.google.com requests. Looking into what is going on with the other ones now.