HTTPS affects more than production encryption. Secure cookies, OAuth redirect URIs, service workers and browser APIs may require a secure context during local development. A trusted local certificate helps test these behaviors without teaching developers to ignore certificate warnings.
Use a local certificate authority tool
A development certificate tool can create a local CA and issue certificates for hostnames such as project.test. Install and trust the CA only on the developer's own machine, then configure Apache, Nginx or a local proxy to use the generated certificate and private key.
Protect the private key
The local CA key is highly sensitive because it can sign certificates trusted by the machine. Keep it out of the project repository, restrict filesystem permissions and never distribute it with the application. Share setup instructions, not private key material.
Configure the web server
Create a TLS virtual host for the local hostname, point it to the correct document root and configure the certificate chain and private key paths. Confirm HTTP redirects to HTTPS only where intended. Keep a separate local configuration so certificate paths do not leak into production deployment files.
Verify browser and application behavior
Open the hostname and inspect the certificate details. Test secure session cookies, absolute URL generation, OAuth callback URLs and mixed-content warnings. A trusted local certificate does not prove production TLS configuration is correct; test the deployed endpoint separately.
Avoid unsafe shortcuts
Do not disable certificate verification in application HTTP clients just to make local requests succeed. Add the development CA to the correct trust store or use an explicit test certificate configuration.
Further reading
- mkcert: https://github.com/FiloSottile/mkcert
- Apache SSL/TLS: https://httpd.apache.org/docs/2.4/ssl/