Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The page provided is not HTML (served as MIME type ).
See original GitHub issueI know there are other issues with a similar name, but they didn’t have a lot of things to try and neither of those worked.
Provide the steps to reproduce
I can’t setup a repo to reproduce it, but I’m attaching the output of curl -vvvv as I saw was asked in another thread.
test.log
AFAICK, the Content-Type is always text/html; charset=UTF-8.
What is the current behavior?
Lighthouse works fine on several URLs of our app, but there is one where it fails with the following message no matter what we do: The page provided is not HTML (served as MIME type ). (The type is missing in the message.)
What is the expected behavior?
The audits finish.
Environment Information
- Affected Channels: CLI and DevTools
- Lighthouse version: 7.2.0 and 7.0.0 respectively
- Chrome version: 89.0.4389.90 (Official Build) (x86_64)
- Node.js version: 15.5.1
- Operating System: macOS Catalina
Related issues https://github.com/GoogleChrome/lighthouse/issues/12125 https://github.com/GoogleChrome/lighthouse/discussions/12097
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Is there a testable URL that you can share? Nothing immediately jumps out to me as problematic in that log, but it would be a lot easier to debug by seeing Chrome make the real request.
Ah, that’s great! I was really having trouble seeing any issue in the curl log and wasn’t sure what other debugging avenues I could explore 😃