Whoever said, “They don’t make bugs like they used to!” when remembering the bad ol’ days…
…well, it seems that that they do :-)
PHP coders are, ahem, chuckling (because there’s no point in crying about it) that the latest security updates include a cryptographic fix that you have to laugh at 😬
Apparently, if you asked PHP to download data with the function file_get_contents(), and used an https:// URL, it would encrypt the connection as expected. (The S in HTTPS means “secure.”)
If you wrote “http://“ (please don’t!) you would get an unencrypted connection over plain HTTP. That’s insecure, but entirely expected.
But if you accidentally wrote an upper-case S in httpS, you wouldn’t get an error. The download would work, but the S would be ignored. You might quite reasonably assume that https, httpS and HTTPS would all behave the same way, given that they were all accepted as valid prefixes. But no! Any connection with an upper-case S would use plain HTTP and be unencrypted, thus leaking important data such as authentication tokens or other HTTP headers as soon as the connection was made.
Patch early, patch often! (The brand new version 8.6.0 came out today and is therefore very first in its series - it does include this fix.)