In DM v220.127.116.11, the 'force schema' key icon next to each domain mapping in a site dash doesn't seem to work. Not in our installation, at least.
I can see (in my browser) the AJAX requests go to the server and the JSON response coming back (with the schema value cycling 0,1,2) and I can see the access log entry on the server but, when I reload the page, the schema reverts back to http://.
[Note to devs: The AJAX request uses the GET verb where it really should be using the PUT (or POST) verb because the request is intended to have a side-effect, namely, to update a setting. That would actually cause a problem for us, but for the WP auth cookies.]
I've tried deleting the mapping and replacing it, but it makes no difference.
Why does this matter? Aside from the obvious apparent bug, Google, in its infinite wisdom, have decided to give SSL-enabled URLs a slight edge in page ranking. They say it isn't much of an advantage but that they might change the weighting they give to SSL later. I suspect that they will.
Moreover, Automattic have announced the intention increasingly to enforce/require SSL, although they haven't yet specified for what they will require SSL.
As a result, I guess I'm going to have to get SSL certs for all the domains I host *sigh*. (Yes, there's LetsEncrypt but that's a bigger PITA than first meets the eye especially if you use Varnish.) Until I do, I want to be able to force SSL on a site-by-site basis rather than force it network wide by the network dash.