I’ll introduce some “real engineer horror stories” I heard recently.

• HTTP Status Code 0
• curl: (35) SSL connect error

Two stories.

HTTP Status Code 0

I heard a scary story about an unheard-of HTTP Status Code 0 being returned, so I researched it.

• HttpSocketResponse HTTP Status becomes 0 - Qiita

It seems that due to bugs in CakePHP or PHP Network libraries, when reasonPhrase is returned with two or more words, the HTTP Status Code isn’t set and becomes 0.

How scary…

curl: (35) SSL connect error

I found an article about ‘curl: (35) SSL connect error’ occurring due to old libcurl versions.

• CentOS6.x libcurl is old causing curl: (35) SSL connect error - Qiita

For announced vulnerabilities, I want to fix them as much as possible by updating libcurl.

• Differences and Vulnerabilities Between SSL and TLS | Symantec

That’s all from the Gemba, where I want to regularly update library versions.