Home/Notes/HTTP to HTTPS: a field note from a bakery
HTTP to HTTPS: a field note from a bakery
22 Jul 2024
How a bakery deals with HTTP to HTTPS — and what usually goes wrong.
The problem: a lastmod stamp that never changes. The certificate chain breaks for a bakery.
We rotate API keys for HTTP to HTTPS annually. a bakery did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.
Most providers let you export HTTP to HTTPS as a zone file. We keep one in version control for every client. If the hosting vanishes, the zone file rebuilds the domain in minutes.
Test HTTP to HTTPS from outside your network before you call it done. Your office Wi-Fi might cache the old answer for another six hours.
Every CMS update brings a small chance that HTTP to HTTPS breaks. For a bakery, we pin versions and test upgrades in a staging copy before touching production.
Nobody at a bakery could remember who had configured HTTP to HTTPS. The credentials were in a text file inside a folder called OLD STUFF on a shared drive.
The fix was to delete the old entry, wait for TTL to expire, and re-add HTTP to HTTPS with the correct value. We scheduled it for 3 AM so nobody lost traffic.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com