Https localhost

Generate https certificate to use for a server running on localhost.

Presentation

@jsenv/https-localhost generates what is needed to start a local server in https:

• a certificate
• a private key

1import { requestCertificateForLocalhost } from "@jsenv/https-localhost"
2
3const { serverCertificate, serverPrivateKey } = await requestCertificateForLocalhost({
4  serverCertificateFileUrl: new URL("./certificates/server.crt", import.meta.url),
5})

Trusting certificate

Every time requestCertificateForLocalhost is executed it checks if the root certificate is trusted. When not, a log explains how to trust it on your OS.

Message when certificate is not trusted on macOS

1Root certificate must be added to macOS keychain
2--- root certificate file ---
3/Users/dmail/Library/Application Support/jsenv_https_localhost/jsenv_root_certificate.crt
4--- suggested documentation ---
5https://support.apple.com/guide/keychain-access/add-certificates-to-a-keychain-kyca2431/mac
6--- suggested command ---
7sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain -p ssl -p basic "/Users/dmail/Library/Application Support/jsenv_https_localhost/jsenv_root_certificate.crt"

It is possible to automate the trusting of the root certificate using tryToTrustRootCertificate.

1import { requestCertificateForLocalhost } from "@jsenv/https-localhost"
2
3const { serverCertificate, serverPrivateKey } = await requestCertificateForLocalhost({
4  serverCertificateFileUrl: new URL("./certificates/server.crt", import.meta.url),
5  tryToTrustRootCertificate: true,
6})

Mapping hosts

Every time requestCertificateForLocalhost is executed it checks if server hostnames are properly mapped to 127.0.0.1 in your hosts file.

Message when hostnames are not mapped on macOS

12 hostnames(s) must be mapped to 127.0.0.1
2--- hostnames ---
3localhost
4*.localhost
5--- hosts file ---
6/etc/hosts
7--- suggested hosts file content ---
8127.0.0.1 localhost
9127.0.0.1 *.localhost

It is possible to automate the update of hosts file using tryToRegisterHostnames.

1import { requestCertificateForLocalhost } from "@jsenv/https-localhost"
2
3const { serverCertificate, serverPrivateKey } = await requestCertificateForLocalhost({
4  serverCertificateFileUrl: new URL("./certificates/server.crt", import.meta.url),
5  tryToRegisterHostnames: true,
6})

On windows tryToRegisterHostnames is ignored, you have to do it manually for now.

Add more alternative names

When you need to make certificate works for other hosts than localhost use serverCertificateAltNames.

1import { requestCertificateForLocalhost } from "@jsenv/https-localhost"
2
3const { serverCertificate, serverPrivateKey } = await requestCertificateForLocalhost({
4  serverCertificateFileUrl: new URL("./certificates/server.crt", import.meta.url),
5  serverCertificateAltNames: ["whatever"], // makes certificate also valid for https://whatever
6})

All host passed in serverCertificateAltNames must be mapped to 127.0.0.1 in your hosts file. This is done for you when tryToRegisterHostnames is enabled.

Usage with node server

1import { createServer } from "node:https"
2import { requestCertificateForLocalhost } from "@jsenv/https-localhost"
3
4const { serverCertificate, serverPrivateKey } = await requestCertificateForLocalhost({
5  serverCertificateFileUrl: new URL("./certificates/server.crt", import.meta.url),
6  tryToTrustRootCertificate: true,
7  tryToRegisterHostnames: true,
8})
9
10const server = createServer(
11  {
12    cert: serverCertificate,
13    key: serverPrivateKey,
14  },
15  (request, response) => {
16    const body = "Hello world"
17    response.writeHead(200, {
18      "content-type": "text/plain",
19      "content-length": Buffer.byteLength(body),
20    })
21    response.write(body)
22    response.end()
23  },
24)
25server.listen(8080)
26
27console.log(`Server listening at https://localhost:8080`)

Installation

1npm install --save-dev @jsenv/https-localhost

Development

If you are part or want to be part of the developpers of this package, check development.md