I was going crazy trying to figure out why I couldn’t make direct secure (HTTPS) connections to wordpress from wbloggar, Chronicle Lite, and other blog posting tools that support secure posting via HTTPS. I thought there was a problem with WordPress, but the problem was actually that my hosting service does not install the PHP curl libraries necessary for such connections.
However, I’m not willing to shoulder all the blame here. 🙂 WordPress is rather silent when it checks to see whether the necessary curl libraries are available. So, my feature request is that you notify users that they cannot make direct secure connections via HTTPS by displaying a message to that effect under the “General Blog Settings” or the “Default Post Options”.
Note that it’s still possible to make HTTPS connections directly to your blog web pages in a browser since that secure connection is managed by your web browser and not by WordPress. The problem I’ve described here only happens when blog posting tools try to connect directly (bypassing HTTP) to wordpress.
- You must be logged in to reply to this topic.