joe.toomey
Forum Replies Created
-
If you want all posts to be SSL only, just don’t check the box the says
Force SSL Exclusively
. I think this option is unfortunately named, b/c I thought it would do the opposite of what it actually does, but the description on the right side of the checkbox is accurate (“Posts and pages without Force SSL enabled will be redirected to HTTP”).I like this idea. I’ll still have to modify their code to build in the SSL Domain mappings, but this will at least allow me to globally request SSL and not have to worry that SSL offloading hides that fact that the user is requesting the page via SSL.
Thanks for this. And please post back if/when you decide to implement the SSL Domain mapping feature.
Thanks!
I was just about to post a new topic when I read your last comment, Mvied. I’m working on making our whole site SSL only including the wordpress blog. We have a load balancer doing SSL offloading and I can configure a site global redirect to take care of all of the content on our site. But we have a wordpress plugin (digg-digg) that has hard coded non-ssl requests for which I can’t simply substitute “https” for “http” (because their use of akamai creates a server identification mismatch). A couple of examples are:
https://static.ak.fbcdn.net/rsrc.php/v1/yN/r/Rp8qyLZw2E2.png
which I need to replace with
https://s-static.ak.fbcdn.net/rsrc.php/v1/yN/r/Rp8qyLZw2E2.png
and
https://w.sharethis.com/button/buttons.js?ver=3.3.1
which I need to replace with
https://ws.sharethis.com/button/buttons.js?ver=3.3.1
(note the hostname changes from w.* to ws.*).
All of this is to say that the SSL Domain mapping feature you describe above would completely solve the problem for me. My current alternative is to work with the digg-digg developers to get a SSL patch, but even that is problematic for me b/c the normal way for digg-digg to determine if they should use the SSL URLs is to test $_SERVER[‘HTTPS’]. But in my case that test will fail (b/c we’re doing SSL offloading and by the time the request gets to our production server, it’s not SSL anymore). Your solution would be ideal for me, so please consider this a big upvote for the direction you described. In the meantime, I’ll probably modify our copy of the digg-digg plugin and offer it to the digg-digg folks as a patch.
Thanks!