Skip to content
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

docs: add instructions for testing with self-signed certificate #9112

Merged
merged 3 commits into from
Jun 4, 2019

Conversation

brendankenny
Copy link
Member

With #8865, --chrome-flags="--ignore-certificate-errors" now works for self-signed certificates. Adds a note to the docs about this so we have a place to point to in the future.

see also #6655, #7292, #7574

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huzzah! 🎉

docs/readme.md Outdated

When testing a site with an untrusted certificate, Chrome will be unable to load the page and so the Lighthouse report will mostly contain errors.

If this certificate **is one you control** and is necessary for development (for instance, `localhost` with a self-signed certificate for local HTTP/2 testing), you can
Copy link
Collaborator

@patrickhulce patrickhulce Jun 4, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO a tad ambiguous if you need to do one or both of these currently, is that intentional to hope they go the trusted cert route? ;)

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

Successfully merging this pull request may close these issues.

4 participants