July/August 2018 issue of acmqueue The July/August issue of acmqueue is out now
Subscribers and ACM Professional members login here



Kode Vicious

Failure and Recovery

  Download PDF version of this article PDF

Error 526 Ray ID: 46e48c1e39da91dc • 2018-10-23 13:28:31 UTC

Invalid SSL certificate

You

Browser

Working
Newark

Cloudflare

Working
deliverybot.acm.org

Host

Error

What happened?

The origin web server does not have a valid SSL certificate.

What can I do?

If you're a visitor of this website:

Please try again in a few minutes.

If you're the owner of this website:

The SSL certificate presented by the server did not pass validation. This could indicate an expired SSL certificate or a certificate that does not include the requested domain name. Please contact your hosting provider to ensure that an up-to-date and valid SSL certificate issued by a Certificate Authority is configured for this domain name on the origin server. Additional troubleshooting information here.

acmqueue

Originally published in Queue vol. 15, no. 1
see this item in the ACM Digital Library


Tweet



Follow Kode Vicious on Twitter
and Facebook


Have a question for Kode Vicious? E-mail him at [email protected]. If your question appears in his column, we'll send you a rare piece of authentic Queue memorabilia. We edit e-mails for style, length, and clarity.


Related:

Peter Alvaro, Severine Tymon - Abstracting the Geniuses Away from Failure Testing
Ordinary users need tools that automate the selection of custom-tailored faults to inject.


Pat Helland, Simon Weaver, Ed Harris - Too Big NOT to Fail
Embrace failure so it doesn't embrace you.


Steve Chessin - Injecting Errors for Fun and Profit
Error-detection and correction features are only as good as our ability to test them.


Michael W. Shapiro - Self-Healing in Modern Operating Systems
A few early steps show there's a long (and bumpy) road ahead.



Comments

(newest first)

Roland | Fri, 14 Jul 2017 16:44:45 UTC

The article is actually about the horror of coding alone. Instead, there should always be a second person, as for code-inspection, peer review, or whatever form of software quality. Then, the usage of TODO / FIXME comments is a great tool. Such comments could even be caught automatically by a clever form of LINT, before reaching production.


Leave this field empty

Post a Comment:







© 2018 ACM, Inc. All Rights Reserved.