Cannot scan sites with self-signed SSL certs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, playwright, typescript
- Domain
- ci-cd, testing-qa
Research direction
Start with the failure path shown in .github/actions/find/dist/findForUrl.js and the find action entry points in .github/actions/find/dist/index.js and bootstrap.js, then trace where the Playwright page or browser context is configured. Add a way to enable the ignoreHTTPSErrors behavior for scans, and verify that the example self-signed HTTPS URL completes instead of aborting the job.
Written by the indexing model from the issue text.
Description
Was giving this tool a little bit of a flex to see how it compares to our Lighthouse workflow, but found that it could not run against our testing environment, since the testing environment uses HTTPS with a self-signed SSL cert.
For context, we set up our testing environment dynamically in GitHub actions, and host it with docker/DDEV. When that environment is up, we can do Lighthouse, Playwright, and Selenium tests against that environment in GitHub CI to a similar degree that a developer could using their own computer.
When the local environment is set up, URLs that follow this pattern are available: https://test.ddev.site/my-test-page. When running this action against that example, we see an error like this:
Starting 'find' action
Preparing to scan https://test.ddev.site/my-test-page
node:internal/modules/run_main:107
triggerUncaughtException(
^
page.goto: net::ERR_CERT_AUTHORITY_INVALID at https://test.ddev.site/my-test-page
Call log:
- navigating to "https://test.ddev.site/my-test-page", waiting until "load"
at findForUrl (/home/runner/work/_actions/github/accessibility-scanner/current/.github/actions/find/dist/findForUrl.js:12:16)
at async Module.default (/home/runner/work/_actions/github/accessibility-scanner/current/.github/actions/find/dist/index.js:14:32)
at async file:///home/runner/work/_actions/github/accessibility-scanner/current/.github/actions/find/bootstrap.js:59:5
at async file:///home/runner/work/_actions/github/accessibility-scanner/current/.github/actions/find/bootstrap.js:31:1 {
name: 'Error'
}
Node.js v24.12.0
That error is thrown, and the rest of the job is completely skipped.
Maybe this action needs a new parameter so that the Playwright environment can use the ignoreHTTPSErrors option?
- Dominant language
- TypeScript
- Stars
- 374
- Forks
- 42
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/accessibility-scanner
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/accessibility-scanner#264 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
github/accessibility-scanner#260 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
github/accessibility-scanner#259 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
github/accessibility-scanner#245 ·
-
Sitemap Support Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
github/accessibility-scanner#244 ·
All issues in github/accessibility-scanner
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100