Skip to content
This repository has been archived by the owner on Jan 4, 2023. It is now read-only.

Service workers missing from 12/15 response bodies #141

Closed
rviscomi opened this issue Jan 3, 2018 · 7 comments
Closed

Service workers missing from 12/15 response bodies #141

rviscomi opened this issue Jan 3, 2018 · 7 comments

Comments

@rviscomi
Copy link
Member

rviscomi commented Jan 3, 2018

For example, this test includes a request for sw.js. It's not in the 12/15 response bodies table, despite the same resource being available in the 12/1 table.

This was originally reported by @jeffposnick in a query similar to this:

SELECT
  DISTINCT url
FROM
  `httparchive.har.2017_12_01_chrome_requests_bodies`
WHERE
  body LIKE '%new self.Workbox%' OR
  body LIKE '%new Workbox%'

This yields 74 results, while a query over the 12_15 table only yields 1 result (the workbox website HTML).

@pmeenan did anything change on the WPT side? This seems like a regression of #113.

@pmeenan
Copy link
Member

pmeenan commented Jan 4, 2018

Looks like it's mostly from Chrome 63 and 2 separate issues.

#1 - 63 started logging some phantom network requests which WPT filtered out but that also filtered out the SW requests (only from dev tools, the netlog had them as well so the requests were still logged but the request ID from devtools was lost and that is used to match the response body. I fixed that which should help.

#2 - We aren't reliably seeing the request for the worker js in dev tools. With the change to plznavigate in 63 it may have broken something there (re-opened the devtools issue and they are looking into it).

@mfalken
Copy link

mfalken commented Feb 1, 2018

Just adding a "Me too!" comment... I work on Chrome's SW implementation and just now tried to use HTTPArchive to investigate how SWs are used in the wild. Would be good to have this working again. On the DevTools issue it looks like there was some clue about off-main-thread-networking?

@pmeenan
Copy link
Member

pmeenan commented Feb 1, 2018 via email

@pmeenan
Copy link
Member

pmeenan commented Feb 1, 2018

This should be fixed now. WebPageTest will backfill any missing response bodies that it couldn't get from the browser by re-fetching them. Not elegant but works. I'll leave it open until we can verify with the Feb 1 crawl (it will be missing for the 1/2 day or so that has been running so far but that's less than 10% of the crawl)

@mfalken
Copy link

mfalken commented Feb 2, 2018

Thank you!

@rviscomi
Copy link
Member Author

SELECT
  DISTINCT url
FROM
  `httparchive.har.2018_02_01_chrome_requests_bodies`
WHERE
  body LIKE '%new self.Workbox%' OR
  body LIKE '%new Workbox%'

Testing against the Feb 1 crawl shows 103 results, so it seems like this has been fixed. Thanks @pmeenan!

@jeffposnick feel free to reopen if you're still seeing issues.

@jeffposnick
Copy link

Looks good! Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants