This console error pops up because the wtml file we are accessing via web.wwtassets.org wants to call the unWISE imageset via an http link instead of https.
Mixed Content: The page at 'https://projects.cosmicds.cfa.harvard.edu/carina/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://alasky.u-strasbg.fr/unWISE/color-W2-W1W2-W1/properties'. This request has been blocked; the content must be served over HTTPS.
If we did a global replacement (in the WWT repos) from http: to https: in all the wtml files that WWT provides, would that cause lots of problems, or would browsers be able to handle https calls to servers that are still actually using http?
This console error pops up because the wtml file we are accessing via
web.wwtassets.orgwants to call the unWISE imageset via an http link instead of https.If we did a global replacement (in the WWT repos) from http: to https: in all the wtml files that WWT provides, would that cause lots of problems, or would browsers be able to handle https calls to servers that are still actually using http?