Securing Crouton’s Kitchen
A reader comments: “I think for a buck or two you can display the secure wwws.irl heading, making many of us more comfortable.”
It took Crouton a minute to figure out what the reader was getting at. When it clicked Crouton realized it was something he’d been meaning to do anyway but didn’t quite know how.
Most websites today are secure, meaning any data you enter is encrypted, making it harder for hackers to get your info. You can tell whether a site is secure by looking at its URL: “http” no, “https” yes. Crouton’s Kitchen isn’t a commercial site, and the only info readers are ever asked to share are their names and email addresses when they submit recipes or comments. Even so, Crouton took his reader’s comment to heart and set about making this site secure.
This is probably more than you wanted to know. But if you’re that one guy or girl, here’s a short explainer titled HTTPS for Dummies — What You Need to Know.
Long story short, Crouton got with his friend Castor Gratin, who hosts the site on his server, and worked it out. Crouton’s Kitchen is now secure. If you have it bookmarked, please update the URL for a more secure experience:
- Crouton’s Kitchen: https://pwoodford.net/cookblog
Big deal? Not to you, maybe, but it is to Crouton, who doesn’t know coding from calculus. Successfully upgrading Crouton’s Kitchen from http to https? This is how it feels to Crouton:
