Certbot is made by the Electronic Frontier Foundation (EFF), a 501(c)3 nonprofit based in San Francisco, CA, that defends digital privacy, free speech, and innovation. - https://certbot.eff.org/. - Source: dev.to / 4 months ago

If you are running this on the internet you could get a valid cert from Let's Encrypt, Certbot could be used to automatically acquire the cert and set it up in major web servers. Source: 11 months ago

If anybody with control over that website is reading this, this is a very solvable problem: Let's Encrypt Certbot. Source: 12 months ago

Set up certbot on your Ubuntu box to get certs automatically for your nginx instance. Source: 12 months ago

a. Using Let's Encrypt: Let's Encrypt is a popular certificate authority that provides free SSL certificates. You can utilize certbot (https://certbot.eff.org/) or a similar tool to automatically generate and renew SSL certificates for your custom domains. This can be integrated into your dynamic nginx configuration generation process. Source: 12 months ago

Basic Scan: the team runs a scan of example.com to determine whether there are any known vulnerabilities in WordPress, plugins, and themes: Wpscan --url https://example.com. - Source: dev.to / 2 days ago

Const express = require('express'); Const cors = require('cors'); Const app = express(); Const corsOptions = { origin: 'https://example.com', methods: ['GET', 'POST'], allowedHeaders: ['Content-Type'], credentials: true }; App.use(cors(corsOptions)); App.get('/data', (req, res) => { res.json({ message: 'This is CORS-enabled for https://example.com' }); }); App.listen(3000, () => { ... - Source: dev.to / 4 days ago

Resource "cloudflare_page_rule" "www-to-non-www-redirect" { zone_id = var.cloudflare_zone_id target = "www.example.com/*" priority = 2 actions { forwarding_url { status_code = 302 url = "https://example.com/$1" } } }. - Source: dev.to / 4 days ago

That’s something different: that’s for upgrading to TLS within the same connection. As in, http://example.com/ → https://example.com:80/, whereas https://example.com/ is https://example.com:443/. I was only a child when RFC 2817 was published, but I’ve never heard of any software that supported it. - Source: Hacker News / 5 days ago

I just tested it. Can't replicate. Went to https://example.com, checked that it's cached in the inspector, clicked on the More information link which leads to https://www.iana.org/domains/example, unplugged my connection (went offline), clicked back. It showed the cached https://example.com. I clicked forward. It showed the cached https://www.iana.org/domains/example page. Clicked back/forward like a maniac, the... - Source: Hacker News / 5 days ago