Bug #7647
closed
- Status changed from New to Reporter Feedback
- Target version set to 1.10.10
Hi Raffi - Thanks for the report.
The issue is with the mapped domain redirect. Mapped domains are stored schemeless in the database (acert.hunter.cuny.edu rather than http://acert.hunter.cuny.edu). Our domain mapping plugin assumes that if you're currently on an HTTPS page, you'll also want to redirect to one - irrespective of whether the mapped domain supports SSL certificates.
In an ideal world, the domain mapping plugin would allow you to specify the scheme of the redirect. This way, we could distinguish at the admin level between mapped domains that support SSL and those that don't. This kind of refactor is beyond what we can do at the moment. So, as a stopgap, I've patched the plugin so that mapped domains are always supposed to have http:// URLs. Those that do support HTTPS will likely perform the necessary redirects themselves once the request hits the webserver.
This change is in place on the production server. Raffi, can you confirm that redirects are now working properly?
For internal reference: https://github.com/cuny-academic-commons/cac/commit/5c2fa3b729d891b435019fe470efd9ed07bdfe7f I'll block wordpress-mu-domain-mapping from auto-updates in the future (though it's not ever updated anyway).
Boone Gorges wrote:
This change is in place on the production server. Raffi, can you confirm that redirects are now working properly?
Confirmed. Thanks!
- Status changed from Reporter Feedback to Resolved
Also available in: Atom
PDF