Option to get around SSL cert issues when curling sitemap locally

[loopy3025]

Problem:

When we run pa11y in local development environments, fetching the sitemap fails, likely due to curl: (60) SSL certificate problem: self signed certificate. Unfortunately,

module.exports = {
  defaults: {
    chromeLaunchConfig: {
      ignoreHTTPSErrors: true,
    }
  }
};

only applies to the tested urls, not curling the sitemap itself.

Possible Solutions:

• A flag that allows us to write a local test script where -k is added to the curl command to fetch the sitemap.
• The ability to pull the sitemap from a file instead. This way, we could curl the sitemap to a folder then read it from there as a file.

Workarounds:

• point to an upstream sitemap. This is our current solution, but it relies on the sitemap being up to date and running. It also precludes the ability to test new features locally with ease. We'd like to be able to add a new page with new features to the sitemap locally and test it before sending it upstream.
• configure certs to every dev environment (NOPE)

[aarongoldenthal]

@loopy3025 As you've seen, pa11y-ci uses fetch (node-fetch specifically) within the Node process to load the sitemap, but the chromeLaunchConfig is only passed to the browser. Until some fix is implemented, you might be able to use something like this to curl the sitemap, extract the urls, and convert them to a list, which pa11y-ci accepts:

$ pa11y-ci $(curl -sk https://somewhere.com/sitemap.xml | sed -n 's:.*<loc>\(.*\)</loc>.*:\1:p' | tr '\n' ' ')

This assumes your sitemap isn't nested, and is not using sitemap find/replace/exclude (although find/replace could be added with sed).