Security without an SSL certificate (we’re too cheap!). I have users on an internal network — if these users can only update the website via a domain name that’s available internally to our network, then I can ensure that no updates are made via the public (external) domain name. I can configure Apache to not allow connections to the Dashboard URLs from the public domain name. I’m currently investigating how I might set this up …
🙂
Thanks, esmi, I’ll dive into that information … I’ve made some headway since my post by using some apache rewrite rules, however I’d like to use the most WordPress-compatible methods possible. I’ll post my final results back here once I’ve set things up how I’d like.
