The problem is the S after the http - get rid of it.... I'm not sure what it is that makes some links Secure but not others..
The S stands for Secure. Without it, your browser connects to the standard HTTP port (80) on the server and fetches the object in the clear. The https prefix tells your browser to connect to a different server TCP port (443), perform a SSL (Secure Sockets Library) handshake, and fetch the object using SSL to encrypt it.
Many web servers support both unencrypted (http) and encrypted (https) connections, but not all. Some web servers don't listen on port 443 at all, so you'll get "connection refused" or something similar. Other web servers (like mine) do listen on 443 but aren't properly set up for every domain name that they happen to serve unless the site owner explicitly pays for that feature. The result can be weird errors, hangs, 404 (not found) errors, etc.
It's a good idea to use https whenever possible just on principle, to make it that much harder for the NSA and other black agencies to vacuum-cleaner the entire web. But if it doesn't work, just change https to http.