-
-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the new head{-less,-full} mode for Chrome #1281
Conversation
In the new
That behaviour makes it behave more like a browser, but causes tests to fail massively:
|
The default 404 response is served as an HTML which skews our asserted metrics. $ curl 0.0.0.0:8888/favicon.ico -I HTTP/1.1 204 No Content Date: Fri, 09 Jun 2023 18:41:05 GMT Connection: keep-alive Server: nginx
# no content for the favicon (the default 404 response is treated as HTML) | ||
location /favicon.ico { | ||
return 204; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will skip including the /favicon.ico
response in the gzipRequests
and htmlCount
metrics.
offenders: | ||
requests: | ||
- { url: "http://127.0.0.1:8888/browser-caching.html", type: "html", size: 517 } | ||
- { url: "http://127.0.0.1:8888/static/jquery-2.1.1.min.js", type: "js", size: 29734 } | ||
- { url: "http://127.0.0.1:8888/favicon.ico", type: "other", size: 103 } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's the cause of all these increased requests
expected values.
Resolves #1279
See https://developer.chrome.com/articles/new-headless/