Home/Notes/A practical look at HTTP to HTTPS for a marina
A practical look at HTTP to HTTPS for a marina
27 Sep 2024
How a marina deals with HTTP to HTTPS — and what usually goes wrong.
The problem: a booking tool that demands an account. The certificate chain breaks for a marina.
Nobody at a marina 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.
We billed a marina two hours for HTTP to HTTPS. The previous agency billed forty hours and left a booking tool that demands an account behind. Complexity is not expertise.
A phishing page copying a marina appeared last year. The only reason their customers could tell it apart was that HTTP to HTTPS was set up correctly on the real site.
HTTPS is table stakes, but HTTP to HTTPS is where trust actually lives for a marina. A padlock with a misconfigured record behind it is decoration, not security.
Fixing HTTP to HTTPS cost less than the lunch meeting where a marina decided to wait another quarter. Waiting is never free.
Maintenance is not glamorous, but it is the reason a marina has not had downtime since we took over HTTP to HTTPS. The invoice is small and the peace of mind is large.
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