You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SSL cert for this URL is invalid: https://cdn.mathjax.org/mathjax/latest/MathJax.js
I realize the notebook code uses http:// for this url but our site uses https:// so when a notebook requests the MathJax.js file it gives an insecure content error.
However, when I hit the URL with https:// it gives an invalid certificate error.
I realize there is an https CDN at Rackspace but notebook only uses it when a certfile is present. We host the notebook for many users so maintaining a certfile in the profile is not practical.
1> Can you install a valid cert for cdn.mathjax.org?
2> Can you make the CDN URL protocol agnostic so it will use the same protocol as the site that is hosting it. In other words, remove the http from the beginning of the URL so it starts with just the two slashes, like this:
//cdn.mathjax.org/mathjax/latest/MathJax.js
The text was updated successfully, but these errors were encountered:
Or you can ship your own copy of mathjax, and serve it from the same server (many people serve mathjax locally on their own laptop, since it's much faster than using a CDN).
The SSL cert for this URL is invalid: https://cdn.mathjax.org/mathjax/latest/MathJax.js
I realize the notebook code uses http:// for this url but our site uses https:// so when a notebook requests the MathJax.js file it gives an insecure content error.
However, when I hit the URL with https:// it gives an invalid certificate error.
I realize there is an https CDN at Rackspace but notebook only uses it when a certfile is present. We host the notebook for many users so maintaining a certfile in the profile is not practical.
1> Can you install a valid cert for cdn.mathjax.org?
2> Can you make the CDN URL protocol agnostic so it will use the same protocol as the site that is hosting it. In other words, remove the http from the beginning of the URL so it starts with just the two slashes, like this:
The text was updated successfully, but these errors were encountered: