{"id":28,"date":"2005-05-18T01:11:24","date_gmt":"2005-05-17T23:11:24","guid":{"rendered":"http:\/\/blog.blackdown.de\/2005\/05\/18\/securing-wordpress-admin-access-with-ssl\/"},"modified":"2016-10-29T03:51:02","modified_gmt":"2016-10-29T01:51:02","slug":"securing-wordpress-admin-access-with-ssl","status":"publish","type":"post","link":"https:\/\/blackdown.de\/articles\/securing-wordpress-admin-access-with-ssl\/","title":{"rendered":"Securing WordPress Admin Access With SSL"},"content":{"rendered":"

January 22nd, 2006:<\/strong> There’s an updated version of this guide for WordPress 2 now: Securing WordPress 2 Admin Access With SSL<\/a><\/em><\/p>\n

As one can guess from the look of this site, I’m using WordPress<\/a> as my blog engine. At this time WordPress does not support HTTPS access to the admin area when the rest of the blog is served via normal HTTP. This is a bit unfortunate. I do not like logging in to my server over unencrypted connections, especially not when using public WLANs. Getting around this WordPress limitation requires quite a few steps:<\/p>\n

The Goal<\/h3>\n

All communication involving passwords or authentication cookies should be done over HTTPS connections. wp-login.php<\/code> and the wp-admin<\/code> directory should only be accessible over HTTPS.
\nNormal reading access, as well as comments, tracebacks, and pingbacks still should go over ordinary HTTP.<\/p>\n

The Plan<\/h3>\n