Global CSS and JS is currently loaded directly from hub (www.shoutwiki.com) which will be on the main HTTPS deployment.
This is one of the trickiest HTTPS fixes we've got to do.
Could we serve this from a specific cached subdomain instead?
Global CSS and JS is currently loaded directly from hub (www.shoutwiki.com) which will be on the main HTTPS deployment.
This is one of the trickiest HTTPS fixes we've got to do.
Could we serve this from a specific cached subdomain instead?
Status | Assigned | Task | ||
---|---|---|---|---|
Open | lewiscawte | T131 Sort HTTPS and make it available to everyone | ||
Open | lewiscawte | T243 Serving on HTTPS | ||
Open | lewiscawte | T244 Global CSS/JS HTTPS readiness |