Generate my own SSL Private Key and Certificate.Reproduce the ignoring of certificate parameters Still, the issue persists that when I restart the webpack-dev-server, the certificate is expiring often, and I need to re-approve it.
Then I see the warning that the certificate is not verified: Rm node_modules/webpack-dev-server/ssl/server.pem I change this "cA" to "CA" in the createCertificate.js file.I can see it gets better when I do the following: If I look into the code, file webpack-dev-server/lib/utils/createCertificate.js, I see the line: It says: "localhost" certificate is not trusted. Open the browser and view the certificate.Start the webpack-dev-server so that it generates the SSL certificate.bin/webpack-dev-server -open -https -cert ~/.ssl/private.pem -key ~/.ssl/private.key For Bugs How can we reproduce the behavior? Reproduce the invalid CA: When accepting it manually, the webpack re-generates that certificate several times per day, and each time the certificate needs to be re-accepted in the browser.Īlso, when trying to pass the self-generated certificates, those parameters get ignored: When starting the webpack-dev-server it generates the SSL certificate which is invalid because it has no CA included. Or, at least allow passing my own certificate from the file, so that I can generate it on the required domain name, and make it valid like 100 years or so. When starting the webpack-dev-server it should generate the SSL certificate which is valid, with the CA, so that when it gets accepted, it doesn't expire each time. Ignored: '**/node_modules/**' Expected Behavior # Inline should be set to true if using HMR
0 kommentar(er)
