Lighthouse doesn't send Accept request header in start_url audit
See original GitHub issueHi!
We are using a service worker that serves HTML pages from cache when the request contains the header Accept: text/html
.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept
We discovered that Lighthouse does not send this header in it’s audit of the start_url
causing the test to result in a false negative.
Failures: Service worker does not successfully serve the manifest's start_url.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Unexplained LightHouse start_url audit error - Stack Overflow
I'm running a PWA LightHouse audit with the ServiceWorker code below. The audit reports failures: - . Current page does not respond with...
Read more >Adding custom headers to origin requests - Amazon CloudFront
These custom headers enable you to send and gather information from your origin that you don't get with typical viewer requests. These headers...
Read more >Lighthouse an open-source, automated tool for improving the ...
Lighthouse powers the Audits panel of Chrome DevTools. ... Stringify\'d JSON HTTP Header key/value pairs to send in requests lighthouse ...
Read more >front_end/core/i18n/locales/en-US.json - devtools/devtools-frontend ...
"message": "This attempt to set a cookie via a Set-Cookie header was blocked because its Domain attribute was invalid with regards to the...
Read more >SEO Spider Configuration - Screaming Frog
You could upload a list of URLs, and just audit the images on them, ... HTTP Headers – This will store full HTTP...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah 4 is the obvious best, but we haven’t done it mostly because it’s slow to add another pass. #4310 should help with the slowness, so after it lands we might be good to just switch to that 👍
@kdzwinel I believe step 4 isn’t as easy as it is because it will need a pass on it’s own to make sure that hte page gets loaded. Doing it in the same pass with other audits will skew the results and can also result in a different final url.